From: Richard Stallman <rms@gnu.org>
To: M Jared Finder <jared@hpalace.com>
Cc: emacs-devel@gnu.org
Subject: Re: C-x C-v considered harmful
Date: Fri, 03 Jul 2009 15:23:34 -0400 [thread overview]
Message-ID: <E1MMoMA-0003nW-Km@fencepost.gnu.org> (raw)
In-Reply-To: <h2jr29$dub$1@ger.gmane.org> (message from M Jared Finder on Thu, 02 Jul 2009 19:40:08 -0700)
keystroke savings seems so minor that I can not imagine ever wanting to.
Is C-x C-v really so much better than C-x k <RET> C-x C-f?
The case where it gave an advantage is that you can enter the
corrected file name based on the mistaken one, rather than starting
from scratch.
But that is not much of an advantage nowadays, because you can get the
mistaken file name via the minibuffer history.
So maybe C-x C-v should be disabled and/or eliminated. But that is
the sort of thing for which the maintainers should poll the users,
rather than just decide on their own.
Miles says
Yes, it's actually quite useful in some cases, and I find I use it
regularly, typically when I've accidentally visited the wrong file -- it
automatically fills in the minibuffer with the old name, so it's usually
very quick to correct the name and hit RET.
Miles, if you had to type
C-x k RET C-x C-f M-p instead of C-x C-v,
in those cases, how painful would that be?
next prev parent reply other threads:[~2009-07-03 19:23 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 1:18 C-x C-v considered harmful Bob Rogers
2009-07-02 2:39 ` Miles Bader
2009-07-02 3:10 ` Bob Rogers
2009-07-02 6:48 ` Kevin Rodgers
2009-07-02 15:17 ` Drew Adams
2009-07-03 1:09 ` Bob Rogers
2009-07-03 3:19 ` Drew Adams
2009-07-03 20:33 ` Bob Rogers
2009-07-03 22:23 ` Drew Adams
2009-07-04 23:16 ` Bob Rogers
2009-07-05 7:13 ` Drew Adams
2009-07-06 0:39 ` Bob Rogers
2009-07-06 1:40 ` Drew Adams
2009-07-07 10:39 ` Johan Bockgård
2009-07-05 10:18 ` Richard Stallman
2009-07-05 14:56 ` Drew Adams
2009-07-05 0:05 ` Richard Stallman
2009-07-05 7:10 ` Drew Adams
2009-07-06 15:05 ` Richard Stallman
2009-07-06 15:59 ` Drew Adams
2009-07-07 10:05 ` Richard Stallman
2009-07-06 12:04 ` Robert J. Chassell
2009-07-06 23:49 ` Juri Linkov
2009-07-07 1:07 ` Drew Adams
2009-07-08 0:32 ` Juri Linkov
2009-07-08 23:28 ` Juri Linkov
2009-07-09 16:09 ` Drew Adams
2009-07-09 22:10 ` Juri Linkov
2009-07-09 22:26 ` Drew Adams
2009-07-09 22:46 ` Juri Linkov
2009-07-09 23:21 ` Drew Adams
2009-07-10 4:05 ` Bob Rogers
2009-07-13 20:05 ` Juri Linkov
2009-07-16 21:57 ` Juri Linkov
2009-07-03 2:40 ` M Jared Finder
2009-07-03 2:57 ` Miles Bader
2009-07-03 19:23 ` Richard Stallman [this message]
2009-07-03 20:07 ` Andreas Schwab
2009-07-03 20:56 ` Miles Bader
2009-07-03 13:55 ` Markus Triska
2009-07-05 22:15 ` Stefan Monnier
2009-07-05 22:42 ` Bob Rogers
2009-07-11 10:06 ` Stefan Monnier
2009-07-14 2:45 ` Bob Rogers
2009-07-14 18:34 ` Stefan Monnier
2009-07-02 21:03 ` Stefan Monnier
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=E1MMoMA-0003nW-Km@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jared@hpalace.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).