From:	"Markus F.X.J. Oberhumer" <k3040e4 AT wildsau DOT idv-edu DOT uni-linz DOT ac DOT at>
Message-Id:	<199801222051.VAA05460@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:	Thu, 22 Jan 1998 21:51:55 +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.980121152908.27671A-100000@is> from "Eli Zaretskii" at Jan 21, 98 03:29:38 pm
Return-Read-To:	k3040e4 AT wildsau DOT idv DOT uni-linz DOT ac DOT at
MIME-Version:	1.0

> >  - should it be bound to a key by default ?
> 
> In the current implementation, it *is* bound.  I think that a program
> which does want to get SIGQUIT, should be able to do that with a
> minimum of hassle.  I certainly think that calling a function which
> binds SIGQUIT to a key is too much of a hassle, especially since it
> has to be done with DJGPP-specific code (which spells #ifdef's in
> ported programs).

While I appreciate your efforts and understand your motivation
behind this patch, I think that is not matured for inclusion
into libc - it's just another dosish hack.

The way to go is termios (fortunately the almighty POSIX argumentation
seems to by on my side this time ;-). Termios offers abstractions of all
the things we need (VINTR, VQUIT, ISIG, ...). It probably needs to get
coupled tighter with the keyboard handler, and there are some things
to be done at startup (like quering KEYB.COM).

I don't know if someone has the motivation and skill to actually
dig into this, but please no more rash libc extensions - if
you need it badly now then put it into emacs.

Markus
(typing this with vi ;-)

-- 
-----   Markus Oberhumer <markus DOT oberhumer AT jk DOT uni-linz DOT ac DOT at>   -----
-----        http://www.wildsau.idv.uni-linz.ac.at/mfx/         -----
-----     5E CB 5C 85 DE AF 9E BF  E9 DA 7E 6A 39 F8 CC 67      -----

                       THREE WARPS TO URANUS

- Raw text -