From: Theodor Thornhill <theo@thornhill.no>
To: "Daniel Martín" <mardani29@yahoo.es>, emacs-devel@gnu.org
Cc: philipk@posteo.net
Subject: Re: master f6967d2 1/3: Allow for the completion buffer to be automatically selected
Date: Wed, 22 Dec 2021 20:39:57 +0100 [thread overview]
Message-ID: <875yrga0oi.fsf@thornhill.no> (raw)
In-Reply-To: <m1sfulwmqp.fsf@yahoo.es>
Daniel Martín <mardani29@yahoo.es> writes:
> I don't think I like this change to the minibuffer defaults. It breaks
> muscle memory and IMO is more incovenient when you need to show the
> completion list many times.
>
Sorry for my ignorance, (and partly offtopic question) but why would you
want to show the completion list many times? Isn't that very slow when
moving around files?
> One typical workflow I have is doing something like C-x C-f TAB TAB to
> see the list of completions and then continue typing to narrow the list
> of completions. After this commit, you need to switch back to the
> minibuffer to continue completing things, which is annoying.
>
This feels very inefficient. Wouldn't it be faster just having the
completion candidates open, then narrowing? I have always found the
default emacs completion system very arcane, but I might be missing
something.
Theo
next prev parent reply other threads:[~2021-12-22 19:39 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 [this message]
2021-12-22 21:18 ` Daniel Martín
2021-12-22 21:30 ` Theodor Thornhill
2021-12-22 23:04 ` Philip Kaludercic
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
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=875yrga0oi.fsf@thornhill.no \
--to=theo@thornhill.no \
--cc=emacs-devel@gnu.org \
--cc=mardani29@yahoo.es \
--cc=philipk@posteo.net \
/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).