You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NOTE: I realize this is not exactly aligned with the menu interface philosophy.
It would be great to have an option for a running console output that does NOT clear the console every time we return to the menu.
A sort-of workaround is to use an input() that just pauses the console to see what the output is before returning to the menu.
But having a full running output would be useful for debugging, especially in dealing with logic errors.
Another workaround would be to test a given function by calling it directly and not relying on doing so via the show_menu interface, but, again, having the option to let the console output run (or tail, if you will) would be great.
Maybe an optional argument (boolean) for the show_menu() function.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
NOTE: I realize this is not exactly aligned with the menu interface philosophy.
It would be great to have an option for a running console output that does NOT clear the console every time we return to the menu.
A sort-of workaround is to use an
input()
that just pauses the console to see what the output is before returning to the menu.But having a full running output would be useful for debugging, especially in dealing with logic errors.
Another workaround would be to test a given function by calling it directly and not relying on doing so via the show_menu interface, but, again, having the option to let the console output run (or tail, if you will) would be great.
Maybe an optional argument (boolean) for the
show_menu()
function.Beta Was this translation helpful? Give feedback.
All reactions