This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author shish
Recipients shish
Date 2008-09-23.21:18:27
SpamBayes Score 1.0684581e-05
Marked as misclassified No
Message-id <1222204708.76.0.512730295083.issue3949@psf.upfronthosting.co.za>
In-reply-to
Content
after the first initscr() sigwinch is handled as expected, but then my 
app needs to ignore sigwinch, leave curses to view the output from 
something, come back into curses, and start listening for sigwinch 
again. The signal(SIGWINCH, SIG_IGN) call doesn't return the old, 
working signal handler; it returns 0 -- thus trying to re-set the 
signal handler doesn't work.

(The reason for ignoring the signal is that if the window is resized 
while the external app is running, python's wait() is interrupted)

Having the handler visible from python would also make curses play 
nicer with readline, as the app could mediate signal handling (see 
issue #3948)
History
Date User Action Args
2008-09-23 21:18:28shishsetrecipients: + shish
2008-09-23 21:18:28shishsetmessageid: <1222204708.76.0.512730295083.issue3949@psf.upfronthosting.co.za>
2008-09-23 21:18:28shishlinkissue3949 messages
2008-09-23 21:18:27shishcreate