Date: Sun, 11 Jan 1998 14:08:20 -0500 (EST)
Message-Id: <199801111908.OAA25285@delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: eliz AT is DOT elta DOT co DOT il
CC: Shawn AT talula DOT demon DOT co DOT uk, robert DOT hoehne AT gmx DOT net, djgpp-workers AT delorie DOT com
In-reply-to: <Pine.SUN.3.91.980111142423.15603B-100000@is> (message from Eli
	Zaretskii on Sun, 11 Jan 1998 14:25:31 +0200 (IST))
Subject: Re: Request for comments: SIGQUIT in DJGPP v2.02
Precedence: bulk


> There are two possible ways to introduce it without such effects:
> either we disable SIGQUIT generation at startup and tell people to
> call `__djgpp_set_sigquit_key' if they want it enabled; or we enable
> it at startup, but define its default handler to be SIG_IGN.  Which
> way do you prefer me to do it?

Of the two, I prefer the second.  How's this sound:

The default handler for SIGQUIT should be SIG_IGN instead of unix's
standard core dump. Even setting SIGQUIT to SIG_DFL should set it to
SIG_IGN.  When SIGQUIT is ignored, that key should be treated as any
other key.

That way, unsuspecting DOS programs won't get surprised, unix programs
expecting SIGQUIT will get it, and other unix programs will think it's
on some other key that the user never hits.