From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Boruch Baum <boruch_baum@gmx.com>
Cc: 43957@debbugs.gnu.org
Subject: bug#43957: remove process-kill-buffer-query-function from kill-buffer-query-functions
Date: Mon, 12 Oct 2020 19:58:34 +0000 [thread overview]
Message-ID: <CADwFkmmmCwRRKUU-9GON5ok5vnNejoTRnRbKZHxrFGje7GZ1Eg@mail.gmail.com> (raw)
In-Reply-To: <83pn5n328x.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> When explicitly killing a shell/eshell or terminal-emulator
>> ansi-term/term buffer, a user shouldn't have to take an extra step to
>> respond to the prompt of process-kill-buffer-query-function. In such
>> cases, the process for which function process-kill-buffer-query-function
>> is activated is the foreground shell process, so of course the conscious
>> user intent is to kill it.
>
> FWIW, I'm not sure an unconditional change in behavior here is TRT.
> Killing a buffer doesn't necessarily imply the user is aware that the
> process will be killed as well.
Indeed. I for one would find an unconditional change here highly
unsettling. I often have a bunch of processes running in the background
and can't be bothered to remember which is running in which buffer.
Getting prompted is important so I don't lose any work.
> I wouldn't object to an opt-in option, though.
Agreed.
next prev parent reply other threads:[~2020-10-12 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 14:07 bug#43957: remove process-kill-buffer-query-function from kill-buffer-query-functions Boruch Baum
2020-10-12 15:14 ` Eli Zaretskii
2020-10-12 19:58 ` Stefan Kangas [this message]
2021-06-06 10:52 ` Lars Ingebrigtsen
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=CADwFkmmmCwRRKUU-9GON5ok5vnNejoTRnRbKZHxrFGje7GZ1Eg@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=43957@debbugs.gnu.org \
--cc=boruch_baum@gmx.com \
--cc=eliz@gnu.org \
/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.