unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Mauro Aranda <maurooaranda@gmail.com>
Cc: 35290-done@debbugs.gnu.org, dgutov@yandex.ru
Subject: bug#35290: 27.0.50; Outdated vc-revert documentation
Date: Tue, 16 Apr 2019 18:28:22 +0300	[thread overview]
Message-ID: <838swageax.fsf@gnu.org> (raw)
In-Reply-To: <CABczVwczBjEpxP7SKMLRAXmitS3oWfhVbL1U3EEYRdWrUWo3Gg@mail.gmail.com> (message from Mauro Aranda on Mon, 15 Apr 2019 19:25:52 -0300)

> From: Mauro Aranda <maurooaranda@gmail.com>
> Date: Mon, 15 Apr 2019 19:25:52 -0300
> Cc: 35290@debbugs.gnu.org
> 
> > Because the section is called "VC Undo", I guess.
> 
> OK.  But I fail to see a reason why a user, after reading the Undo
> section, would expect that M-x undo acts upon anything that is not
> buffer text.  That is what made me think (perhaps wrongly) that the
> sentence is about the old behavior of revert-buffer.
> 
> At the least, I think the documentation could be improved.  Some of the
> things vc-revert does can be reversed (e.g., bring back the reverted
> changes in the affected buffers) and other changes cannot (or might not,
> I'm not sure of the right wording here).  If that is correct, then both the
> current text and my proposed patch fail to make that clear.

OK, I simply removed that sentence from the manual.

Thanks.





  reply	other threads:[~2019-04-16 15:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-15 15:54 bug#35290: 27.0.50; Outdated vc-revert documentation Mauro Aranda
2019-04-15 16:08 ` Mauro Aranda
2019-04-15 16:14 ` Eli Zaretskii
2019-04-15 17:16   ` Dmitry Gutov
2019-04-15 18:19     ` Eli Zaretskii
2019-04-15 20:25       ` Dmitry Gutov
2019-04-15 22:25         ` Mauro Aranda
2019-04-16 15:28           ` Eli Zaretskii [this message]
2019-04-15 17:44   ` Mauro Aranda
2019-04-15 18:23     ` Eli Zaretskii

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=838swageax.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=35290-done@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=maurooaranda@gmail.com \
    /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).