unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: Idea for C-x v u
Date: Wed, 29 Jun 2011 01:55:05 +0200	[thread overview]
Message-ID: <87y60ltsti.fsf@wanadoo.es> (raw)
In-Reply-To: 4E09F937.7060007@swipnet.se

"Jan D." <jan.h.d@swipnet.se> writes:

>>> Why not a customize variable vc-show-diff-before-revert that takes
>>> values yes, no or ask?  Personally I'd set it to no.
>>
>> Really?  If you type `C-x v u' by mistake, you lose your changes with no
>> possibility of retrieval.  If there's anything that needs a yes-or-no
>> prompt, vc-revert is it.
>
> I have never hit C-x v u by mistake.

I have never hit C-x v u by mistake. Sometimes hitted them on the wrong
buffer, though.

[snip]

> Just because something may be lost
> doesn't mean we should add yes-or-no for them all.

AFAIK, yes-or-no exists precisely with the purpose of being more
cumbersome to answer than y-or-no, as a way of saying: "beware: possible
data loss!"

> What if there is important text in a temporary buffer?

That's your fault. As the name implies, temporary buffers are made for
throwing them away.

> Add yes-or-no for C-x k?

C-x k asks for confirmation with yes-or-no-p when the buffer has unsaved
changes.

[snip]




  reply	other threads:[~2011-06-28 23:55 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 [this message]
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

  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=87y60ltsti.fsf@wanadoo.es \
    --to=ofv@wanadoo.es \
    --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).