From: Drew Adams <drew.adams@oracle.com>
To: Marcin Borkowski <mbork@wmi.amu.edu.pl>, help-gnu-emacs@gnu.org
Subject: RE: Looking for a buffer-cycling library
Date: Sun, 16 Nov 2014 12:18:34 -0800 (PST) [thread overview]
Message-ID: <24adfe99-712a-4bb4-ab31-a70deb0cbce6@default> (raw)
In-Reply-To: <87389jt476.fsf@wmi.amu.edu.pl>
> In Ido, I often use C-SPC, which takes what I've typed so far,
> restricts the set of candidates to all the matches and lets my
> type again. This way, I can e.g. type one part of the filename,
> then C-SPC, then another part, then cycle.
>
> AFAIR, in Icicles you can do the same, with the difference
> that keybindings are (probably) different, and the mechanism
> is more general.
Yes. The Icicles key for this is `S-SPC'. I call this feature
"progressive completion". It is typically a lot easier, and
quicker, to incrementally apply simple patterns to match than
it is to try to come up with a single complex pattern that is
equivalent.
http://www.emacswiki.org/Icicles_-_Progressive_Completion
http://www.emacswiki.org/Icicles_-_Nutshell_View#ProgressiveCompletion
A related feature for narrowing choices is what I call "chipping
away the non-elephant": matching candidates that you want to
exclude instead of include.
http://www.emacswiki.org/Icicles_-_Nutshell_View#ChippingAway
next prev parent reply other threads:[~2014-11-16 20:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.13706.1416006724.1147.help-gnu-emacs@gnu.org>
2014-11-15 11:31 ` Looking for a buffer-cycling library Joost Kremers
2014-11-15 14:59 ` Marcin Borkowski
2014-11-15 17:17 ` Drew Adams
2014-11-15 21:04 ` Marcin Borkowski
2014-11-15 23:41 ` Drew Adams
[not found] ` <mailman.13736.1416063601.1147.help-gnu-emacs@gnu.org>
2014-11-16 10:15 ` Joost Kremers
[not found] ` <<slrnm6guar.a37.joost.m.kremers@j.kremers4.news.arnhem.chello.nl>
2014-11-16 17:08 ` Drew Adams
2014-11-16 18:01 ` Marcin Borkowski
2014-11-16 20:18 ` Drew Adams [this message]
2014-11-14 23:11 Tim Johnson
2014-11-15 1:34 ` Alexis
2014-11-15 3:32 ` Tim Johnson
2014-11-15 3:56 ` Alexis
2014-11-15 16:44 ` Tim Johnson
2014-11-15 17:19 ` Drew Adams
2014-11-15 20:32 ` Tim Johnson
2014-11-15 20:38 ` Drew Adams
2014-11-15 22:29 ` Tim Johnson
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=24adfe99-712a-4bb4-ab31-a70deb0cbce6@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=mbork@wmi.amu.edu.pl \
/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).