From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Mattias Engdegård" <mattias.engdegard@gmail.com>,
mwelinder@gmail.com, 58440@debbugs.gnu.org
Subject: bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be
Date: Thu, 13 Oct 2022 21:03:19 +0200 [thread overview]
Message-ID: <87czav7dhk.fsf@gnus.org> (raw)
In-Reply-To: <83k053afhn.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 13 Oct 2022 18:51:48 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> > I'm proposing that we exit on a non-zero value if and when we decide to
>> > exit after a SIGKILL.
>>
>> Done!
>
> That was AFAIU a proposal for discussion, not a request to make the
> change right there and then.
I think that was a joke. 😀
Eli Zaretskii <eliz@gnu.org> writes:
> How do you see that we exit with zero status now? I mean, not by
> looking what the shell says, but by tracing the code which handles
> SIGINT? I'd like to see what code we are talking about before making
> up my mind about the change you propose.
I haven't been able to follow the interrupt handling logic (after
looking at it for a couple minutes), so I don't know.
next prev parent reply other threads:[~2022-10-13 19:03 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87czav7dhk.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.