GNU bug report logs - #58440
27.2; Exit Code on SIGINT is Zero, But shouldn't Be

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: mattias.engdegard <at> gmail.com, mwelinder <at> gmail.com, 58440 <at> debbugs.gnu.org
Subject: bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be
Date: Thu, 13 Oct 2022 13:31:15 +0300

> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Cc: 58440 <at> debbugs.gnu.org,  Eli Zaretskii <eliz <at> gnu.org>,  Morten Welinder
>  <mwelinder <at> gmail.com>
> Date: Thu, 13 Oct 2022 10:12:03 +0200
> 
> Mattias Engdegård <mattias.engdegard <at> gmail.com> writes:
> 
> > Yes, it's the natural outcome in any normal GUI application that
> > doesn't have Emacs's complicated relation to SIGINT.
> >
> > I certainly don't mind if you change Emacs in this respect. 
> 
> I think it'd make sense to change the exit code here -- it seems more
> logical, and I think the potential for breakage is small.  (I mean,
> there may be people that have scripts that rely on Emacs having a zero
> exit code on SIGINT, but it seems rather unlikely.)
> 
> Anybody have any objections to making this change?

What change did you have in mind?  C-g should still raise SIGINT on
TTY frames, so if that's the change you propose, I'm against it.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.