From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Mattias Engdegård" <mattias.engdegard@gmail.com>
Cc: 58440@debbugs.gnu.org, Morten Welinder <mwelinder@gmail.com>,
Eli Zaretskii <eliz@gnu.org>
Subject: bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be
Date: Thu, 13 Oct 2022 10:12:03 +0200 [thread overview]
Message-ID: <87bkqg87n0.fsf@gnus.org> (raw)
In-Reply-To: <62256137-3560-472D-93BF-D353A44D1D56@gmail.com> ("Mattias Engdegård"'s message of "Thu, 13 Oct 2022 10:05:16 +0200")
Mattias Engdegård <mattias.engdegard@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?
next prev parent reply other threads:[~2022-10-13 8:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 13:48 bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be Morten Welinder
2022-10-12 11:22 ` Lars Ingebrigtsen
2022-10-12 14:23 ` Eli Zaretskii
2022-10-12 14:41 ` Lars Ingebrigtsen
2022-10-12 15:40 ` Eli Zaretskii
2022-10-12 15:31 ` Mattias Engdegård
2022-10-12 15:46 ` Lars Ingebrigtsen
2022-10-12 15:54 ` Lars Ingebrigtsen
2022-10-12 17:39 ` Mattias Engdegård
2022-10-13 6:34 ` Lars Ingebrigtsen
2022-10-13 8:05 ` Mattias Engdegård
2022-10-13 8:12 ` Lars Ingebrigtsen [this message]
2022-10-13 10:31 ` Eli Zaretskii
2022-10-13 11:31 ` Lars Ingebrigtsen
2022-10-13 13:16 ` Mattias Engdegård
2022-10-13 15:51 ` Eli Zaretskii
2022-10-13 19:03 ` Lars Ingebrigtsen
2022-10-13 19:35 ` Eli Zaretskii
2022-10-13 16:33 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bkqg87n0.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=58440@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mattias.engdegard@gmail.com \
--cc=mwelinder@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).