From: "Mattias Engdegård" <mattias.engdegard@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
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: Wed, 12 Oct 2022 19:39:11 +0200 [thread overview]
Message-ID: <CBEA83A7-9F99-48EC-B208-F6C41E9CFA0D@gmail.com> (raw)
In-Reply-To: <875ygpavg0.fsf@gnus.org>
12 okt. 2022 kl. 17.54 skrev Lars Ingebrigtsen <larsi@gnus.org>:
> And anyway -- we do exit like we're supposed to, just not with the
> correct value. So I'm not sure this is an explanation for this
> behaviour?
What the correct value is a matter of debate. For instance, it could be argued that SIGINT to a GUI-only Emacs is to be interpreted as a 'please terminate normally' message, in which the exit code 0 may be appropriate.
I have no strong opinion on what it should be (and am not defending status quo); it doesn't seem very important but the original reporter may disagree.
next prev parent reply other threads:[~2022-10-12 17:39 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 [this message]
2022-10-13 6:34 ` Lars Ingebrigtsen
2022-10-13 8:05 ` Mattias Engdegård
2022-10-13 8:12 ` Lars Ingebrigtsen
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=CBEA83A7-9F99-48EC-B208-F6C41E9CFA0D@gmail.com \
--to=mattias.engdegard@gmail.com \
--cc=58440@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--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).