Re: Is SIGWINCH fixed to re-enable it's pre-4.3 behavior? If not, why not?

[L. A. Walsh]

Chet Ramey wrote:

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.

Awesome! (I hope....!)