[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be
From: |
Lars Ingebrigtsen |
Subject: |
bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be |
Date: |
Wed, 12 Oct 2022 17:46:55 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Mattias Engdegård <mattias.engdegard@gmail.com> writes:
>> It does seem like a bug -- I'd expect a non-zero exit code in this case.
>
> It's by design, more or less: see handle_interrupt_signal in
> keyboard.c. Whether that design is desired or not is a different
> matter.
>
> (C-g should probably not generate a signal in the first place; it
> creates more problems than it solves.)
Hm, sounds like it...
But looking at the code:
----
/* The SIGINT handler.
If we have a frame on the controlling tty, we assume that the
SIGINT was generated by C-g, so we call handle_interrupt.
Otherwise, tell maybe_quit to kill Emacs. */
static void
handle_interrupt_signal (int sig)
----
But if I
./src/emacs -Q && echo 'OK'
and then `C-g', that has no effect, but we still hit this logic? And
even if:
(./src/emacs -Q && echo 'OK' )&
where the Emacs definitely isn't attached to the tty, then `C-g' in the
terminal can't have any effect (and doesn't). But we still end up in
this code?
That seems like a bug, possibly?
- bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be, Morten Welinder, 2022/10/11
- bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be, Mattias Engdegård, 2022/10/12
- bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be,
Lars Ingebrigtsen <=
- bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be, Lars Ingebrigtsen, 2022/10/12
- bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be, Mattias Engdegård, 2022/10/12
- bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be, Lars Ingebrigtsen, 2022/10/13
- bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be, Mattias Engdegård, 2022/10/13
- bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be, Lars Ingebrigtsen, 2022/10/13
- bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be, Eli Zaretskii, 2022/10/13
- bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be, Lars Ingebrigtsen, 2022/10/13
- bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be, Mattias Engdegård, 2022/10/13
- bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be, Eli Zaretskii, 2022/10/13
- bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be, Lars Ingebrigtsen, 2022/10/13