From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 43957@debbugs.gnu.org, Boruch Baum <boruch_baum@gmx.com>
Subject: bug#43957: remove process-kill-buffer-query-function from kill-buffer-query-functions
Date: Sun, 06 Jun 2021 12:52:53 +0200 [thread overview]
Message-ID: <87czszs1ru.fsf@gnus.org> (raw)
In-Reply-To: <83pn5n328x.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 12 Oct 2020 18:14:38 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> 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.
>
> I wouldn't object to an opt-in option, though.
I think this sounds a bit obscure as a user option, to be honest. We
already have options covering customisations here. For instance, if
there's certain process connections a user doesn't care about, they can
write hook functions to set `set-process-query-on-exit-flag' for those
processes.
And for this specific change -- to not ask about the process in the
current buffer when issuing the `C-x C-c' command -- I think the user
could easily write a three line function and put that in
`kill-buffer-query-function' instead of `process-kill-buffer-query-function'.
That is, I feel the range of things a user could want to have happen in
this case is so wide that adding a single
`don't-query-about-the-process-in-the-current-buffer' variable would not
significantly help a large enough group of users.
So I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2021-06-06 10:52 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
2021-06-06 10:52 ` Lars Ingebrigtsen [this message]
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=87czszs1ru.fsf@gnus.org \
--to=larsi@gnus.org \
--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 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).