From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: 58404@debbugs.gnu.org
Subject: bug#58404: 29.0.50; [PATCH] When killing Emacs from the last client, don't warn about the session having clients
Date: Mon, 10 Oct 2022 09:11:01 +0300 [thread overview]
Message-ID: <83k058i4y2.fsf@gnu.org> (raw)
In-Reply-To: <20194da7-2318-46db-7536-bbd9e3ddf945@gmail.com> (message from Jim Porter on Sun, 9 Oct 2022 16:32:28 -0700)
> Date: Sun, 9 Oct 2022 16:32:28 -0700
> From: Jim Porter <jporterbugs@gmail.com>
>
> On the other hand, I think it *would* be useful to prompt if you're in
> the last client, but there are other non-client frames. This can happen
> if you start the main Emacs process without --daemon or if you use
> --no-wait. For example:
>
> $ emacs -Q --daemon
> $ emacsclient foo.txt
> $ emacsclient --no-wait -c bar.txt
>
> ;; From the first client:
> M-x save-buffers-kill-emacs
> => This Emacs session has clients; exit anyway?
>
> This is ok, except the prompt could be clearer. The real issue is that
> the session has non-client frames that would get killed.
>
> Attached is a patch to do this.
IMO, this is an unnecessary annoyance. We don't by default ask the
user any questions today, when they want to kill an Emacs session.
Why should we change that in this case? What is the use case where
this command could be invoked by mistake and will risk losing edits or
other valuable work?
next prev parent reply other threads:[~2022-10-10 6:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 23:32 bug#58404: 29.0.50; [PATCH] When killing Emacs from the last client, don't warn about the session having clients Jim Porter
2022-10-10 6:11 ` Eli Zaretskii [this message]
2022-10-10 8:08 ` Jim Porter
2022-10-10 8:53 ` Eli Zaretskii
2022-10-10 16:43 ` Jim Porter
2022-10-10 16:59 ` Eli Zaretskii
2022-10-10 17:49 ` Jim Porter
2022-10-10 17:57 ` Eli Zaretskii
2022-10-10 23:09 ` Jim Porter
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=83k058i4y2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58404@debbugs.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).