unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: Tassilo Horn <tsdh@gnu.org>
Cc: help-gnu-emacs@gnu.org, Jean Louis <bugs@gnu.support>
Subject: Useful completion package in GNU ELPA
Date: Tue, 22 Jun 2021 12:19:27 +0200	[thread overview]
Message-ID: <trinity-ef21dbaf-ed91-4039-a1f1-a75dd96403db-1624357167704@3c-app-mailcom-bs06> (raw)
In-Reply-To: <87sg1a44t1.fsf@gnu.org>


> Sent: Tuesday, June 22, 2021 at 9:28 PM
> From: "Tassilo Horn" <tsdh@gnu.org>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: "Jean Louis" <bugs@gnu.support>, help-gnu-emacs@gnu.org
> Subject: Re: Useful completion package in GNU ELPA
>
> Christopher Dimech <dimech@gmx.com> writes:
>
> Hi Christopher,
>
> > The way you say it sounds very good.  I wonder how it works with
> > orderless and other completion styles such as partial-completion and
> > initials.  Or does aggressive-completion have such capability?
>
> It is agnostic of the used completion-styles but works best for those
> where minibuffer-complete (or rather
> aggressive-completion-auto-complete-fn) can complete the current
> candidate further.  That's the case for styles whose candidates usually
> have a common prefix which can then be completed.
>
> With orderless, because of the orderlessiness, that's less common, e.g.,
> with input fo most styles would have as candidates foo-bar, foo-quux,
> foo-baz and aggressive-completion could complete to foo-.  With
> orderless, baz-foo would also be a canditate so there is no common
> prefix which could be completed.  (Maybe it could complete at least
> "foo" and then it's the users choice if she wants to complete at the
> front or at the end by moving point...).
>
> Similar arguments hold for the flex completion style.
>
> So all in all, I'd say aggressive-completion works very good for the
> styles basic, partial-completion, and substring and less good for more
> "open and flexible" styles.

Have not seen a problem but you seem to have tested it more thoroughly.
Will do some more tests.

> Bye,
> Tassilo
>



  reply	other threads:[~2021-06-22 10:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-21 19:30 Useful completion package in GNU ELPA Jean Louis
2021-06-21 19:48 ` Christopher Dimech
2021-06-21 21:14   ` Jean Louis
2021-06-21 21:24     ` Christopher Dimech
2021-06-22  9:28   ` Tassilo Horn
2021-06-22 10:19     ` Christopher Dimech [this message]
2021-06-22 10:21       ` Tassilo Horn
2021-06-22 10:51         ` Christopher Dimech
2021-06-22 12:26     ` Jean Louis
2021-06-22  1:16 ` Yuchen Pei
2021-06-22  9:24   ` Tassilo Horn
2021-06-22 15:32     ` [External] : " Drew Adams
2021-06-22 15:47     ` Jean Louis

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=trinity-ef21dbaf-ed91-4039-a1f1-a75dd96403db-1624357167704@3c-app-mailcom-bs06 \
    --to=dimech@gmx.com \
    --cc=bugs@gnu.support \
    --cc=help-gnu-emacs@gnu.org \
    --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.
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).