From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 58440@debbugs.gnu.org, mwelinder@gmail.com
Subject: bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be
Date: Wed, 12 Oct 2022 18:40:40 +0300 [thread overview]
Message-ID: <83mta1aw3r.fsf@gnu.org> (raw)
In-Reply-To: <87ilkpayv7.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 12 Oct 2022 16:41:00 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: mwelinder@gmail.com, 58440@debbugs.gnu.org
> Date: Wed, 12 Oct 2022 16:41:00 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > What happens if you say
> >
> > ./src/emacs -Q && echo 'OK'
> >
> > does it say OK when you kill Emacs with SIGINT?
>
> Yes.
That's strange. So the next step is to attach a debugger to Emacs
before delivering SIGINT to it, and see why we don't exit with the
status of 1.
What I verified is that when I do
./src/emacs -Q -nw && echo 'OK'
and then type "kill -INT EMACS-PID" from another terminal, Emacs does
a keyboard quit (i.e. flashes the display and says "Quit" in the
echo-area), which is exactly as I expect. So in the -nw case, the
installed SIGINT handler is called and does what is expected.
next prev parent reply other threads:[~2022-10-12 15:40 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 [this message]
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
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=83mta1aw3r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58440@debbugs.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).