Date: Sun, 18 Jan 1998 11:37:13 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
cc: "Markus F.X.J. Oberhumer" <k3040e4 AT wildsau DOT idv-edu DOT uni-linz DOT ac DOT at>,
        dj AT delorie DOT com, djgpp-workers AT delorie DOT com
Subject: Re: Request for comments: SIGQUIT in DJGPP v2.02
In-Reply-To: <9801161424.AA14898@clio.rice.edu>
Message-ID: <Pine.SUN.3.91.980118113653.18602B-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Fri, 16 Jan 1998, Charles Sandmann wrote:

> The equivalent DJGPP behavior is really CTRL-BREAK.  Maybe this is
> what should be bound to this signal?

I think this is worse than having SIGQUIT enabled by default.  Many
pre-v2.02 programs assume that Ctrl-BREAK causes SIGINT and install a
SIGINT handler to prevent it from aborting.  I'd guess that most of
them don't install a SIGQUIT handler.  So now, when a user presses
Ctrl-BREAK, those programs will abort.  Ctrl-BREAK has higher
probability to be pressed that Ctrl-\.

> You can change the keys which are bound to signals on unix, so there
> is no guarantee that CTRL-\ has anything to do with SIGQUIT anyway.

v2.02 has a provision to change the QUIT key (and the INTR key), so
the same will be possible with DJGPP as well.  A program that needs to
set a specific key to generate SIGINT or SIGQUIT will be able to do
that in v2.01.