From: Juri Linkov <juri@jurta.org>
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: Wed, 31 Aug 2011 12:51:54 +0300 [thread overview]
Message-ID: <87sjohrjfl.fsf@mail.jurta.org> (raw)
In-Reply-To: <CAH8Pv0inA66+ARgCwQzgfwC1b=DeP=hsAwaEvZqeOgAZOhF1=Q@mail.gmail.com> (Dani Moncayo's message of "Wed, 31 Aug 2011 08:22:20 +0200")
> Using the minibuffer would be indeed a way of doing this, but on
> second thought I think that it would be better to have "in-site"
> replacement of the yanked text (like M-y does now), because:
>
> 1. It would be quicker: It saves you the extra <RET> once you have
> selected the wanted entry.
"In-situ" replacement is quicker indeed but has its own problems:
to undo the last yanked text to the initial state you have to undo
insertions and deletions of all intermediate elements of the kill ring.
So what you propose is like setting `search-ring-update' to t in Isearch.
It's quicker without requiring <RET>, but to revert to the initial search
position you have to undo all search movements for intermediate elements of
the search ring.
> 2. When the killed text is tall (has many lines), the minibuffer would
> show only a small fragment of it.
The minibuffer shows enough multi-line text to recognize the wanted entry.
> Thus, for example if you wanted to yank the third entry from the kill
> ring, all you would have to to is "C-y M-p M-p M-p" and you're done.
> Very quick, very intuitive, very convenient!
With many M-p, one extra <RET> is not a problem.
next prev parent reply other threads:[~2011-08-31 9:51 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 [this message]
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
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=87sjohrjfl.fsf@mail.jurta.org \
--to=juri@jurta.org \
--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).