From: Drew Adams <drew.adams@oracle.com>
To: Samuel Wales <samologist@gmail.com>, Tassilo Horn <tsdh@gnu.org>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : Re: can vertico approximate this ido setup?
Date: Sun, 11 Jun 2023 13:26:45 +0000 [thread overview]
Message-ID: <SJ0PR10MB54884648CCFF4C379F6CC32EF357A@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <CAJcAo8tv4vPfNZm_ta+MAk29FDzp6aj_3AOVdv-XZ-FAXhYieg@mail.gmail.com>
>> One thing to note is that with completion-styles
>> (a b c) is that b won't kick in as long as a
>> delivers matches and c won't kick in as long
>> as b finds matches.
>
> aha.
So it doesn't let you see matches for
one or the other. And you don't know
which matched.
The set of matches is a function of
(1) the input domain, (2) your match
patterns, and (3) the matchers/styles.
You can't control #3 interactively,
and #1 is typically determined by the
command/code invoking matching.
That #3 isn't accessible interactively
is OK for some use cases, but overall
it's an inherent design weakness, IMO.
Better to be able to control matching
interactively (and consequently know
what does what) - including #3 (even
#1 to some extent).
Be able to switch among style lists,
including singletons: (c), (a b c),
(b a), (a), (c f),... anytime during
matching/completion.
(Style categories were added, so #3
can at least be predefined now, in
effect allowing more than a single
`completion-styles' value. That's a
start.)
prev parent reply other threads:[~2023-06-11 13:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 1:40 can vertico approximate this ido setup? Samuel Wales
2023-06-04 6:41 ` Michael Albinus
2023-06-04 7:08 ` Samuel Wales
2023-06-04 8:57 ` Tassilo Horn
2023-06-05 1:07 ` Samuel Wales
2023-06-05 7:08 ` Tassilo Horn
2023-06-11 0:54 ` Samuel Wales
2023-06-11 1:05 ` Samuel Wales
2023-06-11 13:26 ` Drew Adams [this message]
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=SJ0PR10MB54884648CCFF4C379F6CC32EF357A@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=samologist@gmail.com \
--cc=tsdh@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.
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.