From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [RFC] Option to kill `emacs --daemon' when closing the last client frame
Date: Thu, 21 Oct 2021 10:34:00 +0300 [thread overview]
Message-ID: <838rymal1z.fsf@gnu.org> (raw)
In-Reply-To: <ed048cc6-fe32-7915-b389-e03d72c85cc9@gmail.com> (message from Jim Porter on Wed, 20 Oct 2021 20:43:31 -0700)
> Cc: emacs-devel@gnu.org
> From: Jim Porter <jporterbugs@gmail.com>
> Date: Wed, 20 Oct 2021 20:43:31 -0700
>
> > We could add an optional command-line argument to do what you want,
> > but I wonder why would that be useful, when we already have
> > kill-emacs.
>
> That's one option, although it might take a bit of work to support that
> (assuming I understand what you mean). As far as I understand how
> ALTERNATE_EDITOR works, there's not an easy way to automatically start
> the Emacs daemon *and* provide it with some extra options. That is,
> ALTERNATE_EDITOR="emacs --daemon --foo" would start the daemon, but
> wouldn't create a client to connect to it.
We could add a new command to the server-client protocol, and make
emacsclient send this command when invoked with the (hypothetical) new
command-line option.
> Another method might be to add an option like
> `daemon-kill-when-no-clients' that defaults to nil. Then after an
> `emacsclient' is killed, we can consult that variable, and if it's true,
> kill the daemon if there are no remaining clients.
That'd require users to modify their init files, which I think is
slightly less desirable than the alternative with a new protocol
command.
next prev parent reply other threads:[~2021-10-21 7:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 4:20 [RFC] Option to kill `emacs --daemon' when closing the last client frame Jim Porter
2021-10-20 4:36 ` Tomasz Konojacki
2021-10-20 20:07 ` Jim Porter
2021-10-21 6:07 ` Eli Zaretskii
2021-10-22 2:42 ` Jim Porter
2021-10-22 6:41 ` Eli Zaretskii
2021-10-23 20:38 ` Jim Porter
2021-10-20 12:13 ` Eli Zaretskii
2021-10-21 3:43 ` Jim Porter
2021-10-21 7:34 ` Eli Zaretskii [this message]
2021-10-22 2:58 ` Jim Porter
2021-10-22 19:51 ` Gregor Zattler
2021-10-23 6:23 ` Eli Zaretskii
2021-10-23 7:45 ` Gregor Zattler
2021-10-23 8:23 ` Eli Zaretskii
2021-10-23 18:41 ` Gregor Zattler
2021-10-25 6:11 ` Jean Louis
2021-10-25 17:18 ` Jim Porter
2021-10-22 11:58 ` Stefan Monnier
2021-10-24 21:49 ` Jim Porter
2021-10-25 6:19 ` Jean Louis
2021-10-25 18:06 ` Jim Porter
2021-10-23 19:57 ` Gregory Heytings
2021-10-24 11:54 ` Gregory Heytings
2021-10-24 15:17 ` Gregory Heytings
2021-11-08 5:13 ` chad
2021-10-25 6:20 ` Jean Louis
2021-10-25 7:37 ` Gregory Heytings
-- strict thread matches above, loose matches on Subject: below --
2021-10-25 22:38 Peter Oliver
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838rymal1z.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jporterbugs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.