From: Sam Halliday <sam.halliday@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: pushing and popping the mark
Date: Sat, 9 May 2015 15:11:20 -0700 (PDT) [thread overview]
Message-ID: <3b561956-c3d1-490b-a02c-6b385cd20fb2@googlegroups.com> (raw)
In-Reply-To: <87wq0h1kzz.fsf@debian.uxu>
On Saturday, 9 May 2015 22:42:21 UTC+1, Emanuel Berg wrote:
> Sam Halliday <sam.halliday@gmail.com> writes:
>
> > 1. go to "new text", kill some relevant text 2.
> > go to "existing text", yank 3. repeat
>
> The best way to do this is to move (once), kill
> everything, move again (once), and yank everything.
>
> So use the kill *ring*.
>
> When you yank, if it isn't what you like, do
> (immediately after the yank) `M-y' for `yank-pop'.
I know this is called `yank-pop`, but it is more of a "peek" because it keeps the kill ring intact.
More generally though, this is a neat solution. I hadn't thought to do it this way. The only problem with it is that it necessitates doing everything in exact order and not making any mistakes along the way. Therefore, I'll prefer `C-x C-x` when there are more than a few things needing moved around, but prefer this in simple cases.
next prev parent reply other threads:[~2015-05-09 22:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-09 11:18 pushing and popping the mark Sam Halliday
2015-05-09 11:30 ` Sam Halliday
2015-05-09 12:49 ` Francis Belliveau
[not found] ` <mailman.2663.1431175800.904.help-gnu-emacs@gnu.org>
2015-05-09 21:08 ` Sam Halliday
2015-05-09 21:15 ` Drew Adams
[not found] ` <mailman.2680.1431206116.904.help-gnu-emacs@gnu.org>
2015-05-09 22:04 ` Sam Halliday
2015-05-09 21:47 ` Emanuel Berg
2015-05-09 22:11 ` Sam Halliday [this message]
2015-05-09 22:34 ` Emanuel Berg
2015-05-10 0:02 ` Drew Adams
[not found] ` <mailman.2683.1431216187.904.help-gnu-emacs@gnu.org>
2015-05-10 1:59 ` Emanuel Berg
2015-05-10 13:41 ` Jude DaShiell
-- strict thread matches above, loose matches on Subject: below --
2015-05-09 15:03 Jude DaShiell
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3b561956-c3d1-490b-a02c-6b385cd20fb2@googlegroups.com \
--to=sam.halliday@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.