From: Augusto Stoffel <arstoffel@gmail.com>
To: Ergus <spacibba@aol.com>
Cc: Daniel Mendler <mail@daniel-mendler.de>,
emacs-devel@gnu.org, Juri Linkov <juri@linkov.net>
Subject: Re: Completions and history
Date: Tue, 12 Apr 2022 19:24:49 +0200 [thread overview]
Message-ID: <87ilre5i5a.fsf@gmail.com> (raw)
In-Reply-To: <20220411174031.2yuh2je5fl3lej7i@Ergus> (Ergus's message of "Mon, 11 Apr 2022 19:40:31 +0200")
On Mon, 11 Apr 2022 at 19:40, Ergus <spacibba@aol.com> wrote:
> On Mon, Apr 11, 2022 at 07:56:58PM +0300, Juri Linkov wrote:
>>> I am wondering if we have some feature to list the minibuffer history
>>> vanilla for example in completions. In ivy there was C-r which switched
>>> completions to the minibuffer-history; icycles had a similar feature;
>>> and helm also had something; but in the default completion system there
>>> is not such feature as far as I know.
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).
next prev parent reply other threads:[~2022-04-12 17:24 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 [this message]
2022-04-12 17:50 ` [External] : " Drew Adams
2022-04-12 18:05 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ilre5i5a.fsf@gmail.com \
--to=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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.