From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: rfrancoise@debian.org, cmr.Pent@gmail.com, 2520@debbugs.gnu.org
Subject: bug#2520: 23.0.91; Dies on SIGHUP
Date: Sun, 29 Sep 2019 15:59:06 +0200 [thread overview]
Message-ID: <87muenjj9x.fsf@gnus.org> (raw)
In-Reply-To: <jwv8wnoq2tm.fsf-monnier+emacsbugreports@gnu.org> (Stefan Monnier's message of "Sun, 01 Mar 2009 17:50:05 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> 1) emacs -Q. Emacs process starts.
>> 2) pkill -s 1 emacs. Emacs process dies.
>
>> The more appropriate behavior would be to reload the configuration
>> without restarting (i.e. reread X resource values). This behavior
>> would be especially useful for the daemon mode.
>
> It could make sense, indeed. It can be pretty problematic as well,
> since most config files read by Emacs (i.e. site-start.el, default.el,
> .emacs) are normally only read a single time per session, and in
> a particular order, at a particular time, so rereading them later on can
> very easily give you unexpected results.
>
> It is a good practice to keep your .emacs file "idempotent", but I think
> such files are the exceptions rather than the rule. So, yes, it could
> be handy, but it would have to come with big warnings "may not do what
> you expect".
So the suggestion here is to make Emacs re-read ~/.emacs on SIGHUP. I
think that sounds like a useful feature -- it would allow you to, for
instance, ssh in to a machine, put (server-start) in ~/.emacs, and then
SIGHUP the Emacs process you want to talk to.
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.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-09-29 13: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 [this message]
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
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=87muenjj9x.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=2520@debbugs.gnu.org \
--cc=cmr.Pent@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=rfrancoise@debian.org \
/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).