From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jim Porter Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] When deleting in bookmark menu, prompt for confirmation. Date: Mon, 3 May 2021 11:28:12 -0700 Message-ID: References: <87a6pcqy7s.fsf@red-bean.com> <83czu86o46.fsf@gnu.org> <835z006jpl.fsf@gnu.org> <87im3z3f8f.fsf@red-bean.com> <83zgxb67g2.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3829"; mail-complaints-to="usenet@ciao.gmane.io" To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon May 03 20:36:39 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lddQs-0000tR-S2 for ged-emacs-devel@m.gmane-mx.org; Mon, 03 May 2021 20:36:38 +0200 Original-Received: from localhost ([::1]:51652 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lddQr-0006gH-Qz for ged-emacs-devel@m.gmane-mx.org; Mon, 03 May 2021 14:36:37 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39218) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lddPP-0005Xq-H4 for emacs-devel@gnu.org; Mon, 03 May 2021 14:35:07 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]:42688) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lddPO-0007n4-2k for emacs-devel@gnu.org; Mon, 03 May 2021 14:35:07 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1lddPK-0009Q6-Ie for emacs-devel@gnu.org; Mon, 03 May 2021 20:35:02 +0200 X-Injected-Via-Gmane: http://gmane.org/ In-Reply-To: <83zgxb67g2.fsf@gnu.org> Content-Language: en-US Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: 5 X-Spam_score: 0.5 X-Spam_bar: / X-Spam_report: (0.5 / 5.0 requ) BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:268832 Archived-At: On 5/3/2021 10:41 AM, Eli Zaretskii wrote: >> From: Karl Fogel >> Cc: Eli Zaretskii , emacs-devel@gnu.org >> Date: Mon, 03 May 2021 12:21:36 -0500 >> >> Backward compatibility is a big deal in an API, but it's a much >> smaller deal in an interactive interface behavior. Yes, users >> will be prompted in a place where they weren't prompted before, >> but the prompt is self-explanatory, and the old behavior was >> needlessly dangerous -- it's easy to type "x" accidentally and >> lose bookmarks marked for deletion before one had finalized the >> list. > > Noted. But we are not going to change the default behavior in > incompatible ways on my watch, sorry. Just a random musing: would there be any sense in adding a global option like `prefer-conservative-defaults' to Emacs 28 and mentioning it in the NEWS so that, come Emacs 29, developers could make modestly backwards-incompatible changes like this while keeping the old behavior for people with `prefer-conservative-defaults' set to t (which they hopefully set upon the release of Emacs 28)? One downside I see right off the bat is that `prefer-conservative-defaults' == t would roughly mean "keep Emacs like it was in version 28", but a decade from now, someone might prefer Emacs 38 and want conservative defaults starting then. I suppose `prefer-conservative-defaults' could specify a preferred version, and `defcustom' could allow for multiple default values defined by particular version ranges. Either of these solutions would increase the maintenance burden somewhat for those variables (the second especially), but no one is *required* to make backwards-incompatible changes, so I'd hope this is only done when a developer truly believes that the new behavior is better, and is worried that existing users won't want to change. This is somewhat academic for me, since I'm an existing user, and I always read the NEWS upon upgrading so I know what, if anything, I'd like to tweak. However, something like this could make it easier to improve Emacs in ways that would make it more attractive to a new user. Like I said, it's just a thought... - Jim