From: Tassilo Horn <tsdh@gnu.org>
To: Manuel Uberti <manuel.uberti@inventati.org>
Cc: emacs-devel@gnu.org
Subject: Re: [GNU ELPA] New package proposal: aggressive-completion.el
Date: Sat, 03 Apr 2021 11:42:02 +0200 [thread overview]
Message-ID: <87y2dzu267.fsf@gnu.org> (raw)
In-Reply-To: <c2a9535a-c4d3-dedd-569f-2207bdc99b6d@inventati.org>
Manuel Uberti <manuel.uberti@inventati.org> writes:
Hi Manuel,
>> I've used several different minibuffer completion frameworks in the
>> past (including ivy, raven, and selectrum) in the past but always
>> came back to the standard emacs minibuffer completion with its nice
>> configuration means in terms of `completion-category-overrides' and
>> friends.
>
> FWIW this has appeared recently: minicomp[1].
>
> It relies on Emacs internals only for completion, maybe it is worth
> checking out?
Probably. :-)
> I've been using for a couple of days now and I like it's minimalistic
> approach.
>
> Note that it may not be what you are after, though. I just wanted to
> offer another recent alternative.
Sure. I'm not sold on vertical display of completions in the echo area
but prefer the column-oriented *Completions* buffer because more
completions are visible at a time. And I prefer having up/down arrows
stick to their usual history navigation commands rather than having them
select between prev/next completion candidate.
Bye,
Tassilo
next prev parent reply other threads:[~2021-04-03 9:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-03 7:53 [GNU ELPA] New package proposal: aggressive-completion.el Tassilo Horn
2021-04-03 8:37 ` Tassilo Horn
2021-04-03 9:11 ` Manuel Uberti
2021-04-03 9:42 ` Tassilo Horn [this message]
2021-04-03 10:14 ` Jean Louis
2021-04-03 11:17 ` Jean Louis
2021-04-03 10:07 ` Jean Louis
2021-04-03 9:36 ` Jean Louis
2021-04-03 10:03 ` Tassilo Horn
2021-04-03 10:19 ` Jean Louis
2021-04-03 10:24 ` Tassilo Horn
2021-04-04 13:53 ` Basil L. Contovounesios
2021-04-04 19:05 ` Tassilo Horn
2021-04-04 20:12 ` T.V Raman
2021-04-05 7:01 ` Tassilo Horn
2021-04-05 14:21 ` T.V Raman
2021-04-04 20:26 ` Stefan Monnier
2021-04-05 7:17 ` Tassilo Horn
2021-04-03 9:49 ` Jean Louis
2021-04-03 10:05 ` Tassilo Horn
2021-04-03 11:53 ` Philip Kaludercic
2021-04-03 11:55 ` Philip Kaludercic
2021-04-03 13:43 ` Tassilo Horn
2021-04-03 17:22 ` [GNU ELPA] New package proposal: aggressive-completion.El Philip Kaludercic
2021-04-03 18:03 ` Tassilo Horn
2021-04-03 14:04 ` [GNU ELPA] New package proposal: aggressive-completion.el Stefan Monnier
2021-04-03 18:29 ` Tassilo Horn
2021-04-03 19:30 ` Tassilo Horn
2021-04-03 21:01 ` Stefan Monnier
2021-04-03 20:02 ` Gabriel
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=87y2dzu267.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=manuel.uberti@inventati.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).