-
Notifications
You must be signed in to change notification settings - Fork 311
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Moving an app into the background and back fails with raw_display #25
Comments
When you hit Here's a way you can handle import signal
def handle_sigcont(signal_number, stack_frame):
# Assuming you can reference urwid's main loop with `loop`
loop.screen.stop()
loop.screen.start()
loop.draw_screen()
signal.signal(signal.SIGCONT, handle_sigcont) I don't know wether the |
raw_display registers a handler for SIGWINCH, that seems like a reasonable place to also register a SIGCONT handler. anyone care to implement this one? |
8013027 should solve this one. |
This is the code for a minimal application from the tutorial:
When I put this application into the background (via CTRL-Z), the cursor of my console disappears. If I then try to move this application back into the forground with the fg command, the text
[1] + continued python minimal.py
is printed but the application is not running again (at least one can't see it). With the following code, everything works as expected: the application can be moved into the background without modifying the cursor and can be moved back into the foreground so the user can continue using the application.wardi from the IRC channel told me to note that there are the signals SIGSTOP, SIGCONT, SIGTSTP, SIGTTIN, and SIGTTOU. Some or maybe all of them may be useful for resolving this issue.
The text was updated successfully, but these errors were encountered: