unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: help-gnu-emacs@gnu.org
Subject: RE: Reverting but keeping undo
Date: Wed, 29 May 2013 06:55:17 -0700 (PDT)	[thread overview]
Message-ID: <93506dfd-1e77-4dec-acad-82872f9bc428@default> (raw)
In-Reply-To: <51A5F3F8.3070300@yandex.ru>

> >> I think it's a great change.
> >>
> > Yes, why?  Any good reason?

You misquoted.  My "why" there was about the lack of discussion prior to this change - why no discussion?  You make it sound like I asked why you thought this was a great change.  Dishonest or an innocent mistake?  This is what you should have quoted:

DG> > I think it's a great change.
da> > > And why no discussion beforehand?
da> Yes, why?  Any good reason?

> > There might well be someone out there who, "personally" or not (?), has
> > (another) good argument for keeping things the way they were - at least as
> > an option.  Who knows?  As Richard often says (especially for changes to
> > basic, longstanding behavior), why not poll the users?
> 
> They should be able to speak up now, or during the pretest. Nothing is
> really set in stone, when it comes to code.

That is not a poll of users.  And it is not a discusson on emacs-devel by Emacs developers.

Instead of willy nilly changing the basic function `revert-buffer', this feature of extra protection against user mistakes (including mistakenly confirming reversion!) should be implemented by creating a separate command or user variable (perhaps option) - giving users the choice to use it or not.  If `auto-revert-mode' is also implicated then it can be made sensitive to the same (or an additional) user choice.

> > Don't you wonder that this came up now seemingly for the first time?  Do
> > you think that no one has thought before about whether the undo list should
> > be kept or dropped when reverting?  A bit presumptuous, no?
> 
> Obviously not. The opened bug is a couple of years old now.

There are thousands of bugs that have been open for a couple of years or more.  That means nothing.

> > Think about it a bit more.  Open it for discussion on emacs-devel.  Why
> > act so precipitously?  Is that "personally" necessary?
> 
> We're having this discussion now, and instead of giving actual reasons
> you're speaking of hypothetical users.

I gave reasons.  1. This is what reverting means, what reverting does (should do, always has done).  2. `revert-buffer' is not used only interactively; it is a basic function used in lots of code.  3. Users should have a choice (individually).

This is like the trash/recycle bin that was added not too long ago.  We didn't just redefine `delete-file' so that it always moves files to the bin, did we?  Why not?

> Talking about personal needs and requirements is good, because every
> person is usually competent about those.
> 
> But the way you often assume the you know the userbase better than
> everyone else is tiresome, to be honest.

I'm not the one assuming anything about the user base.  I'm not the one claiming competence deciding what is good for everyone.   I'm not imposing any change on the existing behavior.  My only assumption about the user base is that users deserve control, choice.



  reply	other threads:[~2013-05-29 13:55 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-15 10:38 Reverting but keeping undo Óscar Fuentes
2013-05-16  5:29 ` W. Greenhouse
2013-05-16 15:10   ` Óscar Fuentes
2013-05-29  1:52 ` Stefan Monnier
2013-05-29  3:09   ` Drew Adams
2013-05-29  3:27     ` Dmitry Gutov
2013-05-29  5:13       ` Drew Adams
2013-05-29 12:26         ` Dmitry Gutov
2013-05-29 13:55           ` Drew Adams [this message]
2013-05-29 15:21             ` Dmitry Gutov
2013-05-29 16:33               ` Drew Adams
2013-05-29 17:51                 ` Dmitry Gutov
     [not found]               ` <mailman.605.1369845207.22516.help-gnu-emacs@gnu.org>
2013-05-29 18:42                 ` Dan Espen
2013-05-29 13:48         ` Stefan Monnier
     [not found]       ` <mailman.562.1369804408.22516.help-gnu-emacs@gnu.org>
2013-05-29 13:25         ` Dan Espen
2013-05-29 16:26           ` Drew Adams
2013-05-30 18:48           ` Michael Heerdegen
2013-05-30 18:41   ` Michael Heerdegen
2013-05-30 19:19     ` Óscar Fuentes
2013-05-30 21:26     ` Stefan Monnier
2013-05-30 22:05       ` Michael Heerdegen
     [not found]       ` <mailman.728.1369951538.22516.help-gnu-emacs@gnu.org>
2013-05-30 23:59         ` Dan Espen
2013-05-31  0:58           ` Stefan Monnier
     [not found]           ` <mailman.738.1369961954.22516.help-gnu-emacs@gnu.org>
2013-05-31  1:21             ` Dan Espen
2013-05-31  2:28               ` Drew Adams
2013-05-31 16:05           ` Michael Heerdegen
2013-05-31 18:29             ` Óscar Fuentes
     [not found]           ` <mailman.767.1370016367.22516.help-gnu-emacs@gnu.org>
2013-05-31 17:22             ` Dan Espen
2013-05-31 18:08               ` Barry Margolin
     [not found]   ` <mailman.699.1369939338.22516.help-gnu-emacs@gnu.org>
2013-05-30 18:45     ` Barry Margolin
  -- strict thread matches above, loose matches on Subject: below --
2013-05-31 16:49 Barry OReilly

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=93506dfd-1e77-4dec-acad-82872f9bc428@default \
    --to=drew.adams@oracle.com \
    --cc=dgutov@yandex.ru \
    --cc=help-gnu-emacs@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.
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).