Zsh Mailing List Archive
Messages sorted by: Reverse Date, Date, Thread, Author

Re: signal weirdness fix

On Nov 26,  8:46am, Zefram wrote:
> Subject: signal weirdness fix
> Remember that odd behaviour I reported, that zsh thought it received a
> signal actually sent to its foreground job?
> This patch limits it to SIGHUP, SIGINT and SIGQUIT, and disables this
> behaviour completely in non-interactive shells.  I think this is a
> semantic.

Actually, I think this is almost exactly the wrong semantic.  The whole
point was so that zsh scripts (which are pretty much by definition not
"interactive shells" even though the script may be doing terminal I/O)
could have their HUP/INT/QUIT traps tripped even when not executing a
builtin command at the time the signal came in.

If you must limit this to some subset of shells (and not just to some
subset of signals), I beg you to choose some other criteria.  I have no
problem with limiting it to HUP/INT/QUIT, but requiring interact is too

Messages sorted by: Reverse Date, Date, Thread, Author