From: "Andreas Röhler" <andreas.roehler@online.de>
To: emacs-devel@gnu.org
Cc: Richard Stallman <rms@gnu.org>
Subject: Re: Idea for C-x v u
Date: Tue, 28 Jun 2011 16:51:55 +0200 [thread overview]
Message-ID: <4E09EA8B.80701@online.de> (raw)
In-Reply-To: <E1QbBW1-0002a5-FS@fencepost.gnu.org>
Am 27.06.2011 15:06, schrieb Richard Stallman:
> 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.
Hi,
think it might pay more to consider the conditions when forgetting occurs.
If it's just to late, a warning might make you still more forgetting.
BTW a feature I most enjoy is abolish warnings when a buffer get's closed.
(defun kill-buffer-unconditional (&optional puffer)
" "
(interactive)
(when puffer
(set-buffer puffer)
(switch-to-buffer (current-buffer))
)
(set-buffer-modified-p 'nil)
(kill-buffer (current-buffer)))
Well, sorry, that's again the opposite direction :)
Seriously: usually run two different VC's at same time: RCS in the
background, committing more often --and without messages-- while above
bazaar or whatever gets it, when it seems done.
Cheers,
Andreas
prev parent reply other threads:[~2011-06-28 14:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 13:06 Idea for C-x v u Richard Stallman
2011-06-27 20:34 ` 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 [this message]
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=4E09EA8B.80701@online.de \
--to=andreas.roehler@online.de \
--cc=emacs-devel@gnu.org \
--cc=rms@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).