GNU bug report logs - #58404
29.0.50; [PATCH] When killing Emacs from the last client, don't warn about the session having clients

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Jim Porter <jporterbugs <at> gmail.com>
Cc: 58404 <at> 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

> Date: Sun, 9 Oct 2022 16:32:28 -0700
> From: Jim Porter <jporterbugs <at> 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?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.