From: Juri Linkov <juri@linkov.net>
To: "João Távora" <joaotavora@gmail.com>
Cc: Ergus <spacibba@aol.com>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>,
"monnier@iro.umontreal.ca" <monnier@iro.umontreal.ca>,
Dmitry Gutov <dgutov@yandex.ru>
Subject: Re: vertical fido-mode
Date: Fri, 19 Jun 2020 01:51:58 +0300 [thread overview]
Message-ID: <87y2okm1gx.fsf@mail.linkov.net> (raw)
In-Reply-To: <CALDnm50eaDnDsJBBrxmumquY_OYKR94pjkFgUL0=cK27RCqBcQ@mail.gmail.com> ("João Távora"'s message of "Thu, 18 Jun 2020 23:41:18 +0100")
>> >> Or maybe it's possible to navigate history using completion lists?
>> >
>> > I'm not sure how that would look.
>>
>> Currently completion is performed on a set of all possible values.
>> In addition to this, completion could be performed on a set of
>> all previously entered values (history items), or on default items
>> (a list of the most useful values). This shows all 3 possibilities:
>>
>> (completing-read "Prompt: "
>> minibuffer-history nil nil nil
>> 'minibuffer-history
>> minibuffer-history)
>>
>> M-n - defaults list, M-p - history list, TAB - completion on history list.
>>
>> In a normal minibuffer maybe there should be a key to switch between
>> normal completion, completion on defaults, and completion on history.
>> Also maybe another key to sort history items by recency/frequency
>> in the completion list.
>
> I think, you are starting to describe incremental reverse history search,
> or C-r in normal minibuffers. It works in icomplete, too, but not too
> well in my opinion. Still, it's better to fix that than to reinvent the wheel.
Actually I meant displaying a list of completions (no matter whether
in the *Completions* buffer or inline like in icomplete) based on
different sets of input data (on all possible values like default completion,
or on all history items...)
next prev parent reply other threads:[~2020-06-18 22:51 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1704199899.1577092.1591806438580.ref@mail.yahoo.com>
2020-06-10 16:27 ` vertical fido-mode Ergus
2020-06-10 16:53 ` Stefan Monnier
2020-06-10 19:01 ` Dmitry Gutov
2020-06-10 19:45 ` Basil L. Contovounesios
2020-06-10 21:54 ` Ergus
2020-06-10 22:00 ` Dmitry Gutov
2020-06-10 23:08 ` Juri Linkov
2020-06-10 23:23 ` Dmitry Gutov
2020-06-11 13:22 ` Ergus
2020-06-11 13:28 ` Noam Postavsky
2020-06-11 13:40 ` Ergus
2020-06-11 15:49 ` Protesilaos Stavrou
2020-06-11 15:52 ` Omar Antolín Camarena
2020-06-11 17:37 ` Basil L. Contovounesios
2020-06-17 21:50 ` Juri Linkov
2020-06-17 21:57 ` Dmitry Gutov
2020-06-17 22:17 ` João Távora
2020-06-17 22:31 ` Drew Adams
2020-06-17 22:40 ` João Távora
2020-06-17 22:56 ` Drew Adams
2020-06-17 22:52 ` Juri Linkov
2020-06-17 23:20 ` Drew Adams
2020-06-17 22:22 ` Juri Linkov
2020-06-17 22:52 ` Dmitry Gutov
2020-06-17 22:57 ` Dmitry Gutov
2020-06-17 22:58 ` Drew Adams
2020-06-17 23:15 ` Drew Adams
2020-06-18 21:54 ` Juri Linkov
2020-06-18 22:41 ` João Távora
2020-06-18 22:51 ` Juri Linkov [this message]
2020-06-19 8:53 ` João Távora
2020-06-18 8:22 ` Kévin Le Gouguec
2020-06-18 10:19 ` Ergus
2020-06-11 13:10 ` Ergus
2020-08-19 12:17 ` Ergus via Emacs development discussions.
2020-08-20 0:35 ` Juri Linkov
2020-08-20 10:37 ` Ergus
2020-08-20 23:15 ` Juri Linkov
2020-08-21 0:05 ` Ergus
2020-08-23 18:45 ` Juri Linkov
2020-08-24 19:06 ` vertical fido-mode (new branch) Ergus via Emacs development discussions.
2020-08-25 18:55 ` Juri Linkov
2020-08-25 23:11 ` Ergus
2020-08-25 23:42 ` Stefan Monnier
2020-08-26 4:34 ` Ergus
2020-08-26 13:30 ` Stefan Monnier
2020-08-28 10:09 ` Ergus
2020-06-10 19:45 ` vertical fido-mode Basil L. Contovounesios
2020-06-11 0:55 Omar Antolín Camarena
2020-06-11 13:03 ` Ergus
2020-06-11 13:44 ` Omar Antolín Camarena
2020-06-11 14:07 ` Ergus
2020-06-11 17:29 ` Basil L. Contovounesios
2020-06-18 13:51 ` Stefan Monnier
2020-06-29 14:44 ` Ergus
[not found] <mailman.50.1591891219.14559.emacs-devel@gnu.org>
2020-06-11 17:06 ` Andrew Schwartzmeyer
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=87y2okm1gx.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--cc=monnier@iro.umontreal.ca \
--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.