Mail Archives: djgpp/1998/01/13/09:41:30
On Tue, 13 Jan 1998, Eli Zaretskii wrote:
> The above is all that's needed to turn on SIGQUIT generation. I
> wanted to avoid even a single line if it isn't necessary. However,
> the few replies that I got seem to indicate that this issue is
> somewhat controversial, and DJ is uneasy about enabling it by
> default. So it seems like SIGQUIT will by default be ignored (i.e.,
> its SIG_DFL action will be to just return), and applications that need
> it will have to turn it on by calling `signal' with a non-default
> handler.
If the user doesn't want Ctrl-\ to abort their program, wouldn't it be
easier to leave SIGQUIT respected but ignore the keypress, rather than
process the Ctrl-\ keypress, generate a SIGQUIT and have it just do
nothing? It seems to me that the dangerous thing is Ctrl-\ generating the
signal in a program which doesn't want that to happen, not the signal's
existence in the first place. Shouldn't a program be able to raise the
signal artificially if it wants to?
--
george DOT foot AT merton DOT oxford DOT ac DOT uk
- Raw text -