From: "Drew Adams" <drew.adams@oracle.com>
To: "'suvayu ali'" <fatkasuvayu+linux@gmail.com>,
"'Oleksandr Gavenko'" <gavenko@bifit.com.ua>
Cc: help-gnu-emacs@gnu.org
Subject: RE: Menu for command history?
Date: Fri, 5 Aug 2011 09:00:18 -0700 [thread overview]
Message-ID: <131A3ECBF93542589BB18234952A714A@us.oracle.com> (raw)
In-Reply-To: <CAMXnza0m6qT8Z0mL4do7dWh-NhnW4iQNY530V_LFYqRD2OXNig@mail.gmail.com>
> > I look for command input history, not for command history.
>
> What about using history completion?
> previous-complete-history-element
> next-complete-history-element
> You can bind these to something for minibuffer-local-*-map
And you can use buffer *Completions* like a menu, if candidate cycling is
available. Your minibuffer input (what's currently in the minibuffer) filters
the possible completions (i.e., filters the menu).
Icicles lets you do this.
* You can also refine the "menu" (candidates) progressively, combining multiple
patterns (e.g., substrings, regexps).
http://www.emacswiki.org/emacs/Icicles_-_Progressive_Completion
* You can also choose multiple candidates (multiple-choice menu).
http://www.emacswiki.org/emacs/Icicles_-_Multiple-Choice_Menus
* You can also, during any minibuffer input (not just with completion), hit
`M-o' to complete against the current minibuffer history, inserting the choice
into the minibuffer.
http://www.emacswiki.org/emacs/Icicles_-_History_Enhancements#toc4
next prev parent reply other threads:[~2011-08-05 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 7:54 Menu for command history? Oleksandr Gavenko
2011-08-05 8:10 ` Jambunathan K
2011-08-05 8:32 ` Oleksandr Gavenko
2011-08-05 9:39 ` suvayu ali
2011-08-05 16:00 ` Drew Adams [this message]
2011-08-05 9:04 ` Andreas Röhler
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=131A3ECBF93542589BB18234952A714A@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=fatkasuvayu+linux@gmail.com \
--cc=gavenko@bifit.com.ua \
--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).