From: Eli Zaretskii <eliz@gnu.org>
To: Carlos Pita <carlosjosepita@gmail.com>
Cc: 51650@debbugs.gnu.org
Subject: bug#51650: Autocomplete: first Tab should show *Completions* buffer
Date: Sun, 07 Nov 2021 09:28:06 +0200 [thread overview]
Message-ID: <83cznca0hm.fsf@gnu.org> (raw)
In-Reply-To: <CAELgYhfXD-0kNGroaHRHd1gwMBPg=wwahnu8dSTZCbf57AucyA@mail.gmail.com> (message from Carlos Pita on Sun, 7 Nov 2021 01:27:44 -0300)
> From: Carlos Pita <carlosjosepita@gmail.com>
> Date: Sun, 7 Nov 2021 01:27:44 -0300
>
> I might be wrong here, but I believe find-file and friends work in a
> way that is a bit inconvenient as well as a bit inconsistent.
>
> For example:
>
> 1. I press C-x C-f and get "Find file: ~/"
> 2. I press Tab once and get the message "Complete, but not unique"
> 3. I press Tab again and the *Completions* buffer appears with
> candidate completions.
> 4. I type "Desk" and press Tab.
> 5. Now I'm at ~/Desktop/ and press Tab again.
> 6. I get the message "Complete, but not unique" but at the same time
> the *Completions* buffer is displayed.
>
> Now, this is inconvenient since the first time I have to type Tab twice
> in order to get the *Completions* buffer (or ?, which is not very
> handy in most keyboards). AFAICS the first Tab does nothing at all
> except in the rare situation when there is a single completion, in
> other cases the inference that the user could use some help seems not
> too far-fetched to me.
This is a long-standing behavior, which is very convenient with file
names. It is documented in the node "Completion Exit" in the Emacs
manual.
We should not change this behavior.
> I think that Tab in step 2 should show the message and the list of
> possible completions at the same time.
That'd get in the way of selecting the "complete, but not unique"
candidate. It is also a distraction.
prev parent reply other threads:[~2021-11-07 7:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-07 4:27 bug#51650: Autocomplete: first Tab should show *Completions* buffer Carlos Pita
2021-11-07 5:09 ` Carlos Pita
2021-11-07 7:29 ` Eli Zaretskii
2021-11-07 8:16 ` Carlos Pita
2021-11-07 8:24 ` Eli Zaretskii
2021-11-07 8:39 ` Carlos Pita
2021-11-07 10:28 ` Eli Zaretskii
2021-11-07 18:40 ` Carlos Pita
2021-11-07 19:00 ` Eli Zaretskii
2021-11-07 19:34 ` Carlos Pita
2021-11-07 19:55 ` Eli Zaretskii
2021-11-07 20:27 ` Carlos Pita
2021-11-07 20:38 ` Eli Zaretskii
2021-11-07 21:21 ` Lars Ingebrigtsen
2021-11-07 21:24 ` Carlos Pita
2021-11-07 22:33 ` Stephen Berman
2021-11-07 7:28 ` Eli Zaretskii [this message]
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=83cznca0hm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51650@debbugs.gnu.org \
--cc=carlosjosepita@gmail.com \
/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).