From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
rfrancoise@debian.org, Stefan Kangas <stefan@marxist.se>,
cmr.Pent@gmail.com, 2520@debbugs.gnu.org
Subject: bug#2520: 23.0.91; Dies on SIGHUP
Date: Fri, 22 Oct 2021 10:59:30 -0400 [thread overview]
Message-ID: <jwv4k99p0lu.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <878rylf93b.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 22 Oct 2021 16:05:44 +0200")
Lars Ingebrigtsen [2021-10-22 16:05:44] wrote:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>>> 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] <...>)
>
> But should Emacs offer something along these lines by default? I think
> it makes some sense to do so, because people only think about adding
> this after the first time they need it. (Well, after the third time,
> because we're too lazy to do it the first couple times around, and just
> swear a lot instead.)
Do we have a `M-x <something>` to re-read the init file?
If not, why would it more important to offer a way to do it via SIGUSR?
Stefan
next prev parent reply other threads:[~2021-10-22 14:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-01 9:07 bug#2520: 23.0.91; Dies on SIGHUP pent
2009-03-01 22:50 ` Stefan Monnier
2009-03-01 23:00 ` Processed: " Emacs bug Tracking System
2019-09-29 13:59 ` Lars Ingebrigtsen
2019-09-29 14:19 ` Andreas Schwab
2019-09-29 15:15 ` Lars Ingebrigtsen
2021-10-22 9:19 ` Stefan Kangas
2021-10-22 12:03 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-22 14:05 ` Lars Ingebrigtsen
2021-10-22 14:59 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-10-22 15:06 ` Lars Ingebrigtsen
2021-10-22 22:31 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-24 12:20 ` Lars Ingebrigtsen
2021-10-24 22:08 ` Stefan Kangas
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=jwv4k99p0lu.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=2520@debbugs.gnu.org \
--cc=cmr.Pent@gmail.com \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=rfrancoise@debian.org \
--cc=schwab@linux-m68k.org \
--cc=stefan@marxist.se \
/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).