From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: Kaushal Modi <kaushal.modi@gmail.com>,
"R. Diez" <rdiezmail-emacs@yahoo.de>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: kill-matching-buffers without confirmation
Date: Mon, 22 May 2017 15:13:15 -0400 [thread overview]
Message-ID: <6ab68316-8d2b-50df-21a7-5a931af15e47@gmail.com> (raw)
In-Reply-To: <CAFyQvY2iAJaHjYA2C=TrD1Z6OMfbEKqo5VgQT_mM58JAZfXNsQ@mail.gmail.com>
On 2017-05-22 15:00, Kaushal Modi wrote:
> A defcustom seems too risky for this. A user can unknowingly copy that var from somewhere and then end up killing modified buffers without confirmation.
I don't think we've applied such a standard before: we have multiple other variables that disable confirmation prompts, like confirm-nonexistent-file-or-buffer, confirm-kill-processes or kill-buffer-query-functions.
> Add a new defun that just sets the new optional arg to non-nil value is less risky as the user would then be knowingly calling the risky variant.
Isn't there a similar risk of a user unknowingly copying code that rebinds the default binding to the risky variant?
Cheers,
Clément.
next prev parent reply other threads:[~2017-05-22 19:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <537757403.6158992.1495470490914.ref@mail.yahoo.com>
2017-05-22 16:28 ` kill-matching-buffers without confirmation R. Diez
2017-05-22 18:21 ` Kaushal Modi
2017-05-22 18:34 ` Clément Pit-Claudel
2017-05-22 18:42 ` Kaushal Modi
2017-05-22 18:45 ` Clément Pit-Claudel
2017-05-22 19:00 ` Kaushal Modi
2017-05-22 19:13 ` Clément Pit-Claudel [this message]
2017-05-22 19:20 ` Kaushal Modi
2017-05-22 19:34 ` Stefan Monnier
2017-05-22 22:21 ` Drew Adams
2017-05-23 5:28 ` Yuri Khan
2017-05-23 6:28 ` R. Diez
2017-05-23 20:34 ` Drew Adams
2017-05-23 12:51 ` Kaushal Modi
2017-05-23 13:03 ` Stefan Monnier
2017-05-23 13:18 ` Kaushal Modi
2017-05-24 1:50 ` zhanghj
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=6ab68316-8d2b-50df-21a7-5a931af15e47@gmail.com \
--to=cpitclaudel@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=kaushal.modi@gmail.com \
--cc=rdiezmail-emacs@yahoo.de \
/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.