From: Drew Adams <drew.adams@oracle.com>
To: Augusto Stoffel <arstoffel@gmail.com>, Ergus <spacibba@aol.com>
Cc: Daniel Mendler <mail@daniel-mendler.de>,
Juri Linkov <juri@linkov.net>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: Completions and history
Date: Tue, 12 Apr 2022 17:50:51 +0000 [thread overview]
Message-ID: <SJ0PR10MB548865BB153ABC0AE09F7D18F3ED9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87ilre5i5a.fsf@gmail.com>
> >>> In ivy there was C-r which switched
> >>> completions to the minibuffer-history;
> >>> icycles had a similar feature;
> >>> and helm also had something;
>
> For the record, Consult provides exactly that command (consult-history)
> and it works beautifully. The same command also works in a few special
> modes like eshell and comint that have a notion of history.
>
> Unlike Ivy, the Consult command is not tied to a specific completion
> framework (I don't know how Icicles is in that regard).
I already said what Icicles offers in this regard.
Whether you consider it a "completion framework"
is up to you. It's just a minor mode - easy to
turn on and off.
With Icicles:
You don't need any separate command, to complete
against the history, any more than with vanilla
Emacs you need a separate command to search, or
to cycle through, the input history.
For any use of the minibuffer (not just for use
with completion), you can at any time get previous
inputs in the usual Emacs ways or by completing.
And for completing there are a couple different
ways. See my previous explanation here:
https://lists.gnu.org/archive/html/emacs-devel/2021-12/msg00949.html
And the doc here:
https://www.emacswiki.org/emacs/Icicles_-_History_Enhancements
next prev parent reply other threads:[~2022-04-12 17:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220411112901.kv3lsyvx6yxwjbph.ref@Ergus>
2022-04-11 11:29 ` Completions and history Ergus
2022-04-11 16:56 ` Juri Linkov
2022-04-11 17:40 ` Ergus
2022-04-12 16:20 ` Juri Linkov
2022-04-12 16:53 ` Ergus
2022-04-12 16:59 ` Ergus
2022-04-12 17:12 ` Juri Linkov
2022-04-12 17:35 ` Ergus
2022-04-12 18:10 ` Juri Linkov
2022-04-12 17:24 ` Augusto Stoffel
2022-04-12 17:50 ` Drew Adams [this message]
2022-04-12 18:05 ` [External] : " Juri Linkov
2022-04-12 19:49 ` Drew Adams
2022-04-13 7:50 ` Juri Linkov
2022-04-13 12:00 ` Augusto Stoffel
2022-04-13 12:12 ` Po Lu
2022-04-14 2:56 ` Richard Stallman
2022-04-13 16:40 ` Drew Adams
2022-04-13 17:58 ` Juri Linkov
2022-04-13 17:57 ` Juri Linkov
2022-04-13 15:49 ` Drew Adams
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=SJ0PR10MB548865BB153ABC0AE09F7D18F3ED9@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=arstoffel@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=mail@daniel-mendler.de \
--cc=spacibba@aol.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).