Date: Sun, 4 Jan 1998 11:34:02 +0200 (IST) From: Eli Zaretskii To: DJ Delorie cc: djgpp-workers AT delorie DOT com Subject: Re: djgpp v2.02 alpha 980101 In-Reply-To: <199801020633.BAA08900@delorie.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Precedence: bulk On Fri, 2 Jan 1998, DJ Delorie wrote: > SIGQUIT: I don't like the idea of redefining a key people are used to > using without having their programs exit. Can we do this a > different way? We could always disable it by default (by making the QUIT key variable be zero). However, I'm not sure that in practice this is a real problem. What programs will be affected by this change? Can you name some of them? The GNU packages can't be victims of this, since Ctrl-\ generates SIGQUIT on Unix. So those programs who need to disable SIGQUIT already take care of this problem. Programs that switch the console to raw binary mode disable Ctrl-\ as well as Ctrl-C, since the same bit in __djgpp_hw_int_flags disables both of them. So it seems that we are looking for programs which do NOT switch stdin to binary mode, but still use Ctrl-\ for some functionality. Does anybody know about such programs? Would asking about this on c.o.m.d. (to reach wider audience) be a good idea? The reason I don't like having SIGQUIT disabled by default is that it will require DJGPP-specific code to switch it on in programs that do want to catch SIGQUIT differently than SIGINT (yes, I have examples of such programs).