unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: uzibalqa <uzibalqa@proton.me>
To: Emanuel Berg <incal@dataswamp.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: completion-styles with increasing level of matching
Date: Mon, 01 Aug 2022 15:25:32 +0000	[thread overview]
Message-ID: <zp1eAU48jPzvp1B5SwS_1ONT6h4DOx3-J57OtXJELmao4PcM0y_ZrJkWV8--o4s8B1kx_ZriYhU2RNvNB01r-qfn_ZzYnRMNgmju7yP8SuU=@proton.me> (raw)
In-Reply-To: <87czdkccm0.fsf@dataswamp.org>






Sent with Proton Mail secure email.

------- Original Message -------
On Monday, August 1st, 2022 at 1:33 PM, Emanuel Berg <incal@dataswamp.org> wrote:


> uzibalqa via Users list for the GNU Emacs text editor wrote:
>
> > Are `flex' and` initials' considered frequently useful?
>
>
> Depends who you ask ...
>
> > Which isthe most aggressive from the two?
>
>
> Depends what property that is and how it is
> measured/estimated ...

`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?




  reply	other threads:[~2022-08-01 15:25 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 [this message]
2022-08-01 15:34     ` Emanuel Berg
2022-08-01 21:38       ` Samuel Wales

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='zp1eAU48jPzvp1B5SwS_1ONT6h4DOx3-J57OtXJELmao4PcM0y_ZrJkWV8--o4s8B1kx_ZriYhU2RNvNB01r-qfn_ZzYnRMNgmju7yP8SuU=@proton.me' \
    --to=uzibalqa@proton.me \
    --cc=help-gnu-emacs@gnu.org \
    --cc=incal@dataswamp.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).