From: Philip Kaludercic <philipk@posteo.net>
To: "Daniel Martín" <mardani29@yahoo.es>
Cc: Theodor Thornhill <theo@thornhill.no>, emacs-devel@gnu.org
Subject: Re: master f6967d2 1/3: Allow for the completion buffer to be automatically selected
Date: Wed, 22 Dec 2021 23:04:23 +0000 [thread overview]
Message-ID: <87sfukb5s8.fsf@posteo.net> (raw)
In-Reply-To: <m1lf0cqqxz.fsf@yahoo.es> ("Daniel Martín"'s message of "Wed, 22 Dec 2021 22:18:16 +0100")
Daniel Martín <mardani29@yahoo.es> writes:
> But on master the implemented solution was more
> or less an intermediate one where the completion list was not shown
> automatically and the results were not filtered "on the fly". IMO, that
> kind of intermediate solution doesn't help much to attract people used
> to that kind of workflow from other applications/Emacs packages, and
> only annoy people used to vanilla completion.
The motivation was not to attract people from either side, but to fix an
annoyance I had when a string couldn't be expanded, but was not unique.
With completion-auto-select disabled you either have to edit the
minibuffer yourself, or switch to the *Completions* buffer using the
(imo inconvenient) M-v key. The idea is that completion-auto-select and
completion-wrap-movement provide is a method to reduce all completion
operations to a single key (tab), without having to change modifiers.
(Looking back, I understand the change was too radical for the master
branch, though I still think that it is a considerable improvement, and
provides a basis upon which incremental narrowing could be implemented,
without falling for a lot of the issues that other popular "frameworks"
have)
> Another experiment that might be more successful is to enable an ELPA
> package like mct[1] by default, and offer a single option to revert to
> the default minibuffer behavior, for people used to vanilla completion.
I don't see how this is any better or worse than enabling
completion-auto-select by default.
--
Philip Kaludercic
next prev parent reply other threads:[~2021-12-22 23:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m1sfulwmqp.fsf.ref@yahoo.es>
2021-12-21 23:40 ` master f6967d2 1/3: Allow for the completion buffer to be automatically selected Daniel Martín
2021-12-22 8:58 ` Juri Linkov
2021-12-22 9:27 ` Po Lu
2021-12-22 11:07 ` Lars Ingebrigtsen
2021-12-22 17:59 ` Juri Linkov
2021-12-22 9:48 ` tomas
2021-12-22 13:48 ` Philip Kaludercic
2021-12-22 17:45 ` Juri Linkov
2021-12-22 20:02 ` Philip Kaludercic
2021-12-23 6:34 ` Eli Zaretskii
2021-12-23 17:23 ` Juri Linkov
2021-12-23 18:44 ` [External] : " Drew Adams
2021-12-22 19:39 ` Theodor Thornhill
2021-12-22 21:18 ` Daniel Martín
2021-12-22 21:30 ` Theodor Thornhill
2021-12-22 23:04 ` Philip Kaludercic [this message]
2022-05-31 17:56 ` Juri Linkov
2022-06-03 8:57 ` Philip Kaludercic
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=87sfukb5s8.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=mardani29@yahoo.es \
--cc=theo@thornhill.no \
/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.