From: Tomasz Konojacki <me@xenu.pl>
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: Wed, 20 Oct 2021 06:36:41 +0200 [thread overview]
Message-ID: <20211020063638.8963.5C4F47F8@xenu.pl> (raw)
In-Reply-To: <sko5ei$45k$1@ciao.gmane.io>
On Tue, 19 Oct 2021 21:20:35 -0700
Jim Porter <jporterbugs@gmail.com> wrote:
> I've been experimenting with using `emacs --daemon' and found one part of it to be somewhat surprising. If I set `ALTERNATE_EDITOR' to the empty string and run emacsclient, it runs `emacs --daemon' and connects to it; so far so good. But when I close the Emacs client, the Emacs daemon sticks around; I'd prefer the daemon to stop as well.
>
> This would allow for a behavior similar to other (graphical) programs: if I run `firefox example.com', it starts a new instance as normal. If I run it again, it opens a new tab in the existing instance. If I close all the Firefox windows, all the associated processes terminate.
>
> I didn't see any options to configure this behavior in Emacs, but looking over the code, it shouldn't be that hard for me to write a patch to add this as an option. Before I started though, I wanted to see what others thought. Is this a behavior others would be interested in? If so, are there any other particulars I should take into account in my patch?
>
> - Jim
You will get that behaviour if you put (server-start) in your init.el
and set --alternate-editor to the emacs binary, not just an empty string.
next prev parent reply other threads:[~2021-10-20 4:36 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 [this message]
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
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
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=20211020063638.8963.5C4F47F8@xenu.pl \
--to=me@xenu.pl \
--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 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).