From: Gregory Heytings <gregory@heytings.org>
To: Jean Louis <bugs@gnu.support>
Cc: Jim Porter <jporterbugs@gmail.com>, emacs-devel@gnu.org
Subject: Re: [RFC] Option to kill `emacs --daemon' when closing the last client frame
Date: Mon, 25 Oct 2021 07:37:27 +0000 [thread overview]
Message-ID: <822aec9d013cb9dee849@heytings.org> (raw)
In-Reply-To: <YXZMtK0kSm944LVQ@protected.localdomain>
>
> I did not see your message, this is exact idea I had, you have already
> written it, but did you test it? Does it work?
>
There's a improved version in bug#51377, which also checks whether there
are unsaved file-visiting modified buffers and running processes before
killing the daemon. And yes, it works.
next prev parent reply other threads:[~2021-10-25 7:37 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
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 [this message]
-- 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=822aec9d013cb9dee849@heytings.org \
--to=gregory@heytings.org \
--cc=bugs@gnu.support \
--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.