[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#2520: 23.0.91; Dies on SIGHUP
From: |
Stefan Monnier |
Subject: |
bug#2520: 23.0.91; Dies on SIGHUP |
Date: |
Fri, 22 Oct 2021 08:03:40 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) |
Stefan Kangas [2021-10-22 02:19:21] wrote:
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>> Andreas Schwab <schwab@linux-m68k.org> writes:
>>> On Sep 29 2019, Lars Ingebrigtsen <larsi@gnus.org> wrote:
>>>> It's definitely something I could have used a number of times... and
>>>> re-reading init files on SIGHUP isn't an unusual thing to do.
>>> But only for demons. Normally a process receives SIGHUP if its
>>> controlling terminal goes away.
>> Yeah, that's true.
>> I guess SIGUSR1 and 2 are also taken...
Not really: they're turned into input events and one of them can be used
for `debug-on-event` but the other is free.
> So do we actually want to do anything here? Simply re-reading the
> configuration comes with its own set of complications for us.
BTW, if someone wants to re-read their init file upon SIGUSR1, they can
do so via something like:
(define-key special-event-map [sigusr1] <...>)
-- Stefan
- bug#2520: 23.0.91; Dies on SIGHUP, Stefan Kangas, 2021/10/22
- bug#2520: 23.0.91; Dies on SIGHUP,
Stefan Monnier <=
- bug#2520: 23.0.91; Dies on SIGHUP, Lars Ingebrigtsen, 2021/10/22
- bug#2520: 23.0.91; Dies on SIGHUP, Stefan Monnier, 2021/10/22
- bug#2520: 23.0.91; Dies on SIGHUP, Lars Ingebrigtsen, 2021/10/22
- bug#2520: 23.0.91; Dies on SIGHUP, Stefan Monnier, 2021/10/22
- bug#2520: 23.0.91; Dies on SIGHUP, Lars Ingebrigtsen, 2021/10/24
- bug#2520: 23.0.91; Dies on SIGHUP, Stefan Kangas, 2021/10/24