[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Is SIGWINCH fixed to re-enable it's pre-4.3 behavior? If not, why no
Re: Is SIGWINCH fixed to re-enable it's pre-4.3 behavior? If not, why not?
Mon, 19 Sep 2016 15:29:13 -0400
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
On 9/19/16 12:38 PM, L. A. Walsh wrote:
> It sounds like, from the release notes, that allowing real-time processing
> of signal handlers in read should no longer be an issue if pselect
> is used to before read to allow waiting for and processing of real-time
> events before reading a character.
Correct. SIGWINCH will interrupt a pselect() and allow the shell, or any
other application using readline, to run a signal hook outside of any
signal handling context.
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU address@hidden http://cnswww.cns.cwru.edu/~chet/