From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: kill-matching-buffers without confirmation Date: Mon, 22 May 2017 15:34:18 -0400 Message-ID: References: <537757403.6158992.1495470490914.ref@mail.yahoo.com> <537757403.6158992.1495470490914@mail.yahoo.com> <126b99e9-6af4-0ed7-2f8b-aee7e04c3022@gmail.com> <6ab68316-8d2b-50df-21a7-5a931af15e47@gmail.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1495481679 8453 195.159.176.226 (22 May 2017 19:34:39 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 22 May 2017 19:34:39 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon May 22 21:34:34 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dCt6A-000248-Fx for ged-emacs-devel@m.gmane.org; Mon, 22 May 2017 21:34:34 +0200 Original-Received: from localhost ([::1]:44542 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dCt6F-0004VJ-QT for ged-emacs-devel@m.gmane.org; Mon, 22 May 2017 15:34:39 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38909) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dCt69-0004VE-Ox for emacs-devel@gnu.org; Mon, 22 May 2017 15:34:34 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dCt65-00085O-S7 for emacs-devel@gnu.org; Mon, 22 May 2017 15:34:33 -0400 Original-Received: from [195.159.176.226] (port=33435 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dCt65-00085A-LH for emacs-devel@gnu.org; Mon, 22 May 2017 15:34:29 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1dCt5w-0001kk-9y for emacs-devel@gnu.org; Mon, 22 May 2017 21:34:20 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 17 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:mxGV3xGmz7SPYmWsV35WKOaaGrg= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:215105 Archived-At: >> 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. Killing a modified buffer means throwing away data without any way to recover it, so it's kind of "almost always dangerous". In contrast confirm-nonexistent-file-or-buffer is never dangerous, confirm-kill-processes can be dangerous but it very much depends, and kill-buffer-query-functions (which *is* dangerous as well) is not a defcustom. Stefan