From: David De La Harpe Golden <david@harpegolden.net>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 9406@debbugs.gnu.org
Subject: bug#9406: 24.0.50; Use M-p/M-n to navigate through the kill ring
Date: Fri, 02 Sep 2011 02:24:07 +0100 [thread overview]
Message-ID: <4E603037.9030508@harpegolden.net> (raw)
In-Reply-To: <CAH8Pv0jzTSfEW2ZEi5wT1BBnWe=nRsHQ70V1mB+Yib+KncFswg@mail.gmail.com>
On 01/09/11 22:56, Dani Moncayo wrote:
>>> users would not be able to browse
>>> the kill-ring in the minibuffer just after yanking the top entry with
>>> C-y.
>>
>> They are browsing it in-place with M-y
>
> In-place browsing would be already doable in a more convenient way
While default behaviour of M-y is obviously wastefully useless without
the preceding C-y, default behaviour of C-y M-y is long-standing [1].
While (cough) I am not exactly one to balk at a change to a
long-standing default just because it's long-standing (and hey it's not
at all up to me anyway, Stefan's already been pretty positive), you do
just have to expect some people to think an idea to change such a
long-standing default is not quite as great as you may think it is.
"More convenient" is also somewhat subjective - for one thing, if M-y's
present behaviour after C-y is gone and you have to use M-n/M-p instead,
you have to switch from y to n/p (even when touch typing properly, n is
on the same finger as y on qwerty), whereas you do get to stay on y for
M-y/M-C-y, and of course (as already mentioned) you can't press M-n/M-p
for their normal functionality in some mode directly after a C-y anymore.
Presumably, the latter would just mean learning to hit C-g after C-y if
you're about to press M-n to go to the next slime compiler note or
whatever, so (as already mentioned) I do not actually strongly object to
special meaning of M-n/M-p after C-y, so long as M-n/M-p are not
globally bound even without a preceding C-y (a global binding would
discourage the IMO pleasant current "mode-appropriate next/prev" common
usage, as ISTR being mentioned under another different recent proposal
for an M-n/M-p binding on emacs-devel). Still I suspect you just happen
to not already use M-n/M-p nearly as much as some people like myself.
[1]
http://bzr.savannah.gnu.org/lh/emacs/trunk/annotate/476/lisp/simple.el#L768
http://bzr.savannah.gnu.org/lh/emacs/trunk/annotate/476/lisp/simple.el#L1630
(and it was presumably there before that date, rev 476 is just when
simple.el got imported into version control, at least the version
control that our present history has a lineage all the way back to)
next prev parent reply other threads:[~2011-09-02 1:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 11:39 bug#9406: 24.0.50; Use M-p/M-n to navigate through the kill ring Dani Moncayo
2011-08-30 12:08 ` Juri Linkov
2011-08-30 12:17 ` Dani Moncayo
2011-08-30 12:27 ` Juri Linkov
2011-08-30 18:13 ` Deniz Dogan
2011-08-30 18:48 ` Dani Moncayo
2011-08-31 6:22 ` Dani Moncayo
2011-08-31 9:51 ` Juri Linkov
2011-08-31 10:45 ` Dani Moncayo
2011-08-31 13:01 ` Stefan Monnier
2011-08-31 13:55 ` Deniz Dogan
2011-08-31 14:33 ` Thierry Volpiatto
2011-08-31 14:52 ` Deniz Dogan
2011-09-02 0:39 ` Stefan Monnier
2011-08-31 15:40 ` Dani Moncayo
2011-08-31 15:45 ` Deniz Dogan
2011-08-31 16:11 ` Drew Adams
2011-08-31 15:33 ` Dani Moncayo
2011-08-31 15:47 ` David De La Harpe Golden
2011-08-31 16:36 ` Juri Linkov
2011-08-31 21:18 ` Dani Moncayo
2011-09-01 8:42 ` Juri Linkov
2011-09-01 9:13 ` Dani Moncayo
2011-09-01 9:53 ` Antoine Levitt
2011-09-01 10:28 ` Dani Moncayo
2011-09-01 13:22 ` Juri Linkov
2011-09-01 14:44 ` Dani Moncayo
2011-09-01 19:59 ` David De La Harpe Golden
2011-09-01 21:56 ` Dani Moncayo
2011-09-02 1:24 ` David De La Harpe Golden [this message]
2022-04-27 14:21 ` Lars Ingebrigtsen
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=4E603037.9030508@harpegolden.net \
--to=david@harpegolden.net \
--cc=9406@debbugs.gnu.org \
--cc=dmoncayo@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).