From: Carlos Pita <carlosjosepita@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 51650@debbugs.gnu.org
Subject: bug#51650: Autocomplete: first Tab should show *Completions* buffer
Date: Sun, 7 Nov 2021 05:39:40 -0300 [thread overview]
Message-ID: <CAELgYhe8YbxpwqF83ONzEsZYXH5fr7yQrFYim47RQABjKhGhFg@mail.gmail.com> (raw)
In-Reply-To: <838ry09xvi.fsf@gnu.org>
> > *Completions* buffer: one won't do it, exactly two won't always do
> > it (both of them may complete something), so there must be a
> > sequence of at least two Tabs and the last one must be unable to
> > complete.
>
> The 2 TABs are necessary if the partial completion is not what you
> want. Emacs cannot know that, only you, the user, can.
But then, by the same token, why is this not true of step 5?
There I'm in ~/Desktop coming from a previous completing Tab, a "not
unique" message was not yet shown, I might press Tab again and get
another completion (perhaps there is a single subdirectory of
~/Desktop, perhaps all subdirectories share a common prefix) or not
(by far the most likely case). I press Tab and get "not unique" plus
candidates.
Suppose I now abort the process and do `M-x cd ~/Desktop` and then
enter the find-file completion again, I'm in the same situation, yet I
press Tab and I get "not unique" and I have to press Tab again in
order to get the list of candidates. Why should the behavior differ?
The only difference is that current != previous command, but that
seems hardly relevant to the matter.
next prev parent reply other threads:[~2021-11-07 8:39 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 [this message]
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
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=CAELgYhe8YbxpwqF83ONzEsZYXH5fr7yQrFYim47RQABjKhGhFg@mail.gmail.com \
--to=carlosjosepita@gmail.com \
--cc=51650@debbugs.gnu.org \
--cc=eliz@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.
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).