From: Richard Stallman <rms@gnu.org>
To: emacs-devel@gnu.org
Subject: Idea for C-x v u
Date: Mon, 27 Jun 2011 09:06:13 -0400 [thread overview]
Message-ID: <E1QbBW1-0002a5-FS@fencepost.gnu.org> (raw)
It is definitely a good idea to check the diffs of a file before
reverting a change, but normally it's a waste of time for C-x v u to
do that because I will have done it manually.
However, if I ever forget to do that, it wouldn't hurt for C-x v u to
remind me.
So here's an idea. Make C-x v d record the tick count of the buffer
when it was done. Then C-x v u can show a diff, if you have not made
one of that buffer since the last edit in it.
This might be universally better than the two optional choices that
were previously proposed (either unconditionally show a diff, or never
show a diff).
Another idea is: if you have not made a diff since the last change in
the buffer, give an error, "Please look at a diff using C-x v = before
doing C-x v u". It is more convenient for the user to make the diff
with a separate command than to examine it inside of yes-or-no-p.
Even if C-x v u does not make a diff, it should always call
yes-or-no-p.
--
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org, www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
Use free telephony http://directory.fsf.org/category/tel/
next reply other threads:[~2011-06-27 13:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 13:06 Richard Stallman [this message]
2011-06-27 20:34 ` Idea for C-x v u Jan Djärv
2011-06-27 23:03 ` Richard Stallman
2011-06-28 6:00 ` Jan Djärv
2011-06-28 6:18 ` David Kastrup
2011-06-28 8:27 ` Jan Djärv
2011-06-28 14:58 ` Chong Yidong
2011-06-28 15:47 ` David Kastrup
2011-06-29 10:58 ` Richard Stallman
2011-06-28 15:54 ` Jan D.
2011-06-28 23:55 ` Óscar Fuentes
2011-06-29 5:56 ` Jan D.
2011-06-29 8:52 ` David Kastrup
2011-06-29 6:51 ` Andreas Röhler
2011-06-29 8:06 ` Jan D.
2011-06-30 17:26 ` Stefan Monnier
2011-06-30 20:34 ` Drew Adams
2011-06-28 14:51 ` Andreas Röhler
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1QbBW1-0002a5-FS@fencepost.gnu.org \
--to=rms@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.