unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jim Porter <jporterbugs@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: [PATCH] When deleting in bookmark menu, prompt for confirmation.
Date: Mon, 3 May 2021 11:28:12 -0700	[thread overview]
Message-ID: <s6pfbp$1719$1@ciao.gmane.io> (raw)
In-Reply-To: <83zgxb67g2.fsf@gnu.org>

On 5/3/2021 10:41 AM, Eli Zaretskii wrote:
>> From: Karl Fogel <kfogel@red-bean.com>
>> Cc: Eli Zaretskii <eliz@gnu.org>,  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




  reply	other threads:[~2021-05-03 18:28 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-03  3:43 [PATCH] When deleting in bookmark menu, prompt for confirmation Karl Fogel
2021-05-03  9:16 ` Lars Ingebrigtsen
2021-05-03 12:48   ` Stefan Kangas
2021-05-03 13:02     ` Stefan Monnier
2021-05-04  7:53     ` Lars Ingebrigtsen
2021-05-04 16:29       ` [External] : " Drew Adams
2021-05-03 11:41 ` Eli Zaretskii
2021-05-03 12:47   ` Stefan Kangas
2021-05-03 13:16     ` Eli Zaretskii
2021-05-03 15:43       ` Stefan Kangas
2021-05-03 16:25         ` Eli Zaretskii
2021-05-03 17:21         ` Karl Fogel
2021-05-03 17:41           ` Eli Zaretskii
2021-05-03 18:28             ` Jim Porter [this message]
2021-05-03 18:44               ` Eli Zaretskii
2021-05-03 19:01                 ` Jim Porter
2021-05-03 20:52             ` Karl Fogel
2021-05-05  5:24             ` Karl Fogel
2021-05-05  8:11               ` Lars Ingebrigtsen
2021-05-05 19:37                 ` Karl Fogel
2021-05-05 20:06                   ` Stefan Monnier
2021-05-05 21:38                     ` Karl Fogel
2021-05-05 23:17                       ` [External] : " Drew Adams
2021-05-05 23:25                         ` Karl Fogel
2021-05-06  6:52                         ` Matthias Meulien
2021-05-06 15:29                           ` Drew Adams
2021-05-08 20:46                             ` Matthias Meulien
2021-05-09  8:54                               ` Eli Zaretskii
2021-05-09 18:37                                 ` Karl Fogel
2021-05-09 18:39                                   ` Eli Zaretskii
2021-05-25  5:38                                     ` Karl Fogel
2021-05-25 12:09                                       ` Eli Zaretskii
2021-05-25 20:24                                         ` Karl Fogel
2021-05-26 11:59                                           ` Eli Zaretskii
2021-05-26 19:33                                             ` Karl Fogel
2021-05-07 17:42                           ` Karl Fogel
2021-05-07 22:24                             ` Drew Adams
2021-05-08  6:13                               ` Karl Fogel
2021-05-06  8:49                   ` Lars Ingebrigtsen
2021-05-06 13:30                     ` Stefan Monnier
2021-05-07  8:40                       ` Lars Ingebrigtsen
2021-05-07 12:55                         ` Stefan Monnier
2021-05-09  9:55                           ` Lars Ingebrigtsen
2021-05-09 15:04                             ` Stefan Kangas
2021-05-09 18:01                               ` Stefan Monnier
2021-05-10  8:30                               ` Lars Ingebrigtsen
2021-05-07 17:40                     ` Karl Fogel
2021-05-05 11:56               ` Eli Zaretskii
2021-05-05 21:43                 ` Karl Fogel
2021-05-03 17:43           ` [External] : " Drew Adams

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='s6pfbp$1719$1@ciao.gmane.io' \
    --to=jporterbugs@gmail.com \
    --cc=emacs-devel@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).