From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>, help-gnu-emacs@gnu.org
Subject: RE: updating buffer window while accepting minibuffer input
Date: Wed, 16 Jul 2014 18:43:12 -0700 (PDT) [thread overview]
Message-ID: <d7c635a5-ba9e-4887-b609-426840079b5d@default> (raw)
In-Reply-To: <87iomwrem7.fsf@web.de>
> In Icicles' search, use the normal candidate exclusion mechanism.
Which means:
1. Type a pattern to match whatever subset of the current
set of candidates you want to remove (exclude, subtract).
2. Then use `C-~' to remove them.
See "Chip Away the Non-Elephant" in the Icicles doc:
http://www.emacswiki.org//Icicles_-_Nutshell_View#ChippingAway
next prev parent reply other threads:[~2014-07-17 1:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.161.1405526455.3403.help-gnu-emacs@gnu.org>
2014-07-16 21:12 ` updating buffer window while accepting minibuffer input Buchs, Kevin J.
2014-07-16 21:50 ` Drew Adams
2014-07-17 0:52 ` Michael Heerdegen
2014-07-17 1:43 ` Drew Adams [this message]
2014-07-17 2:43 ` Michael Heerdegen
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=d7c635a5-ba9e-4887-b609-426840079b5d@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/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).