From:	"Markus F.X.J. Oberhumer" <k3040e4 AT wildsau DOT idv-edu DOT uni-linz DOT ac DOT at>
Message-Id:	<199801182043.VAA02185@wildsau.idv.uni-linz.ac.at>
Subject:	Re: Request for comments: SIGQUIT in DJGPP v2.02
To:	eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date:	Sun, 18 Jan 1998 21:43:36 +0100 (MET)
Cc:	k3040e4 AT wildsau DOT idv-edu DOT uni-linz DOT ac DOT at, dj AT delorie DOT com,
	djgpp-workers AT delorie DOT com
In-Reply-To:	<Pine.SUN.3.91.980118113605.18602A-100000@is> from "Eli Zaretskii" at Jan 18, 98 11:36:45 am
Return-Read-To:	k3040e4 AT wildsau DOT idv DOT uni-linz DOT ac DOT at
MIME-Version:	1.0

> I don't understand this comment.  If a program installs a handler for
> SIGQUIT, it should not have any surprises with this change, since
> pressing the QUIT key will just call that handler.  So what does
> bother you, exactly?

I'm still very unhappy

- because many programs currently install SIGQUIT handlers out of
  paranoia, but none of them *wants* to receive SIGQUIT

- because SIGQUIT keys are highly localized - I have to press 
  the following 3 keys on my German keyboard (thanks Tom):
  Ctrl + AltGr (this is the right Alt) + sharp s (which is the '-' next
  to the '0' on an US keyboard)

- because I'm not sure what is good for ;-) - why do yo need it,
  and why do you think that many programs need it ?

- Raw text -