From: Drew Adams <drew.adams@oracle.com>
To: Sam Halliday <sam.halliday@gmail.com>, help-gnu-emacs@gnu.org
Subject: RE: pushing and popping the mark
Date: Sat, 9 May 2015 17:02:58 -0700 (PDT) [thread overview]
Message-ID: <271b7cb1-f3c3-4c37-8d3b-1b257c1fdcd3@default> (raw)
In-Reply-To: <3b561956-c3d1-490b-a02c-6b385cd20fb2@googlegroups.com>
> > `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.
There are plenty of ways to more directly access given entries on
the kill-ring. `browse-kill-ring[+].el' provides one. Icicles
provides another, and I'm sure that other general completion
packages do too now.
Quite often, when vanilla Emacs provides only a way to cycle, to
get to some candidate, some package such as Icicles gives you a
way to get to it more directly.
Whether it is navigating among function-definition tag matches
or among index matches in Info, the vanilla Emacs approach is
often to have you repeatedly hit a key (e.g. `M-,') to get to
successive candidates, but completion packages let you
pattern-match against all candidates (and cycle among the
matches, if you like).
Even vanilla Emacs sometimes gives you more direct ways, in
addition to mechanically cycling. To get to a previous
minibuffer (history) entry, for example, you need not cycle to
it using `M-p' over and over. You can sometimes reach it more
directly by matching, using `M-r'. Or even better, using `C-r'
(in the minibuffer - see (emacs) `Isearch Minibuffer'). I'm
not saying that these vanilla matching means are wonderful,
but they sometimes exist and are underused.
Sometimes cycling is handier than matching; sometimes the
reverse - depending on how long the candidate list is and
whether partial matching shortens the list to be cycled.
Icicles and other packages that combine matching with cycling
usually let you get where you are going pretty directly.
Compared to using `yank-pop', for example, being able to get
to any marked locations anywhere, by matching, or by a
combination of matching and cycling, sure beats just cycling.
next prev parent reply other threads:[~2015-05-10 0:02 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
2015-05-09 22:34 ` Emanuel Berg
2015-05-10 0:02 ` Drew Adams [this message]
[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
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=271b7cb1-f3c3-4c37-8d3b-1b257c1fdcd3@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=sam.halliday@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.
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).