From: Samuel Wales <samologist@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: completion-styles with increasing level of matching
Date: Mon, 1 Aug 2022 14:38:38 -0700 [thread overview]
Message-ID: <CAJcAo8sU+eu_nrZa1YUo+7x47j5GH9Fvb8N8vda63m4TPuvEvg@mail.gmail.com> (raw)
In-Reply-To: <87r120asgn.fsf@dataswamp.org>
fwiw i don't use completion-styles yet i think, but i use ido +
ido-hacks + ido-clever match. ido [with flex] and i discover short
shorthands for e.g. org headers for refiling. those need not be
initials. and rarely would initials work for me.
i think if you use completion-styles, whether you need flex will
depend on whether you use more than initials.
[idk if fido or the new composable stuff will be able to emulate my
setup. if it does then maybe it will use completion-styles.]
On 8/1/22, Emanuel Berg <incal@dataswamp.org> wrote:
> uzibalqa wrote:
>
>> `flex' attempts to complete using in-order substrings, so
>> `foo' matches `frodo' or `fbarbazoo'.
>> Whereas `initials' complete acronyms and initialisms such that
>> `lch' matches `list-command-history'.
>>
>> They seem to do the same thing to me. Any good insight what
>> one can do but the other can't?
>
> While I do rely on chemical, cognitive and physical speed the
> physical part of that is typing so I'm the worst person to ask
> actually ;)
>
> --
> underground experts united
> https://dataswamp.org/~incal
>
>
>
--
The Kafka Pandemic
A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com
prev parent reply other threads:[~2022-08-01 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 13:05 completion-styles with increasing level of matching uzibalqa via Users list for the GNU Emacs text editor
2022-08-01 13:33 ` Emanuel Berg
2022-08-01 15:25 ` uzibalqa
2022-08-01 15:34 ` Emanuel Berg
2022-08-01 21:38 ` Samuel Wales [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
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=CAJcAo8sU+eu_nrZa1YUo+7x47j5GH9Fvb8N8vda63m4TPuvEvg@mail.gmail.com \
--to=samologist@gmail.com \
--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).