From: bramadams <adams.bram@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Move yanked entry to front of kill ring instead of other way around
Date: Mon, 26 Nov 2007 08:17:12 -0800 (PST) [thread overview]
Message-ID: <5b0819e7-b752-4d93-ab4d-b7ccfddfaf3b@e6g2000prf.googlegroups.com> (raw)
In-Reply-To: 35e81a0c-c827-41b7-bbfe-7395ef5ec900@s36g2000prg.googlegroups.com
Hi,
On 22 nov, 17:34, bramadams <adams.b...@gmail.com> wrote:
> However, I wonder whether there is also some solution where the most
> recently yanked entry is physically transferred to the front of the
> ring instead of the other way around. Of course, in that case the ring
> is not really a pure ring anymore...
I've been browsing a bit through the elisp manual (http://www.gnu.org/
software/emacs/manual/html_node/elisp/The-Kill-Ring.html#The-Kill-
Ring), and the behaviour above apparently is not that easy to obtain.
Advising functions would be the way to go, but there may be some
problems with the interplay between yanking and undoing.
Suppose the ring contains ("a" "b" "c") with "a" as the oldest entry.
If one presses C-y followed by M-y, one should not immediately move
the resulting "b" to the front of the kill ring, as there could be
other M-y or C-_ invocations before the current yank process ends,
i.e. the actual desired data is found. Then, the ring's front should
move back to its original position, with the yanked data moved to the
front (if needed).
Did anyone ever try to pursue something similar, i.e. change the
current kill ring behaviour?
Kind regards,
Bram Adams
next prev parent reply other threads:[~2007-11-26 16:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 10:48 Move yanked entry to front of kill ring instead of other way around bramadams
2007-11-22 5:54 ` Kevin Rodgers
[not found] ` <mailman.3931.1195711151.18990.help-gnu-emacs@gnu.org>
2007-11-22 8:45 ` bramadams
2007-11-22 16:07 ` Mathias Dahl
2007-11-22 16:34 ` bramadams
2007-11-26 16:17 ` bramadams [this message]
2007-12-05 17:08 ` Mathias Dahl
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=5b0819e7-b752-4d93-ab4d-b7ccfddfaf3b@e6g2000prf.googlegroups.com \
--to=adams.bram@gmail.com \
--cc=help-gnu-emacs@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.
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).