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 19:59:57 +0300 [thread overview]
Message-ID: <834jwbhawi.fsf@gnu.org> (raw)
In-Reply-To: <c488bd2f-ec2e-cec8-db76-59e9f24b644a@gmail.com> (message from Jim Porter on Mon, 10 Oct 2022 09:43:55 -0700)
> Date: Mon, 10 Oct 2022 09:43:55 -0700
> Cc: 58404@debbugs.gnu.org
> From: Jim Porter <jporterbugs@gmail.com>
>
> Here's why I think prompting then makes sense: when you're in an
> emacsclient frame and there are other non-client frames (i.e. ones
> "owned" by the main Emacs process), that looks very similar to the user
> as when you have a second emacsclient running.
No, there's a very fundamental difference between the two. When there
are client frames showing buffers, for each client buffer there's a
process waiting, the process which requested the buffer to be edited.
That's why we prompt: we don't want to fail those waiting processes.
Non-client frames don't have this problem.
next prev parent reply other threads:[~2022-10-10 16:59 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
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 [this message]
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=834jwbhawi.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).