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 21:00:13 +0200 [thread overview]
Message-ID: <83zgqf7pvm.fsf@gnu.org> (raw)
In-Reply-To: <CAELgYhfr0RV-hKJJhNOZ2wcsAOHed-7cxexTcyPooY6o60WO3w@mail.gmail.com> (message from Carlos Pita on Sun, 7 Nov 2021 15:40:22 -0300)
> From: Carlos Pita <carlosjosepita@gmail.com>
> Date: Sun, 7 Nov 2021 15:40:22 -0300
> Cc: 51650@debbugs.gnu.org
>
> I remain unconvinced. I'll restate the above in a slightly more
> precise manner, but other than that I have nothing to add and if this
> is getting tiresome by all means feel free to close it.
>
> > > 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?
> >
> > Because you haven't typed anything yet, so Emacs doesn't know what you
> > have in mind. In the other case, it has some hint.
>
> For me the relevant state includes:
>
> - I'm in the ~/Desktop directory.
> - I've not yet received any information about ~/Desktop being unique or not.
>
> By adding one of:
>
> - I've reached ~/Desktop from ~/Desk by pressing Tab.
> - I've reached ~/Desktop by launching Emacs from ~/Desktop.
> - I've reached ~/Desktop by changing the working directory.
> etc.
>
> ... or, more succinctly:
>
> - I've reached ~/Desktop by (immediately before) pressing Tab during
> the same "completing session".
> - I've reached ~/Desktop by other means.
>
> ... I can make the relevant state different, but I cannot grasp how
> the added information is relevant. You say in the first case I have
> typed something, namely Tab, but that was in a different context
> (~/Desk) and I don't find it more relevant than the fact that I have
> typed "M-x cd ~/Desktop" in the second example. What's that thing that
> the user has in mind?
>
> If the "not unique" message were shown at the end of step 4 instead,
> that would make an arguably relevant difference. In this variant, the
> first Tab (both in 2 and in 4) is always the one conveying the "not
> unique" hint, in 2 it's required only for this. Now in step 5 the
> information set includes: "I know that ~/Desktop is not unique", while
> this information is missing from the scenario in which I reached
> ~/Desktop by, say, launching emacs from that directory. I still find
> this inconvenient but it's a way of resolving what I see as
> inconsistent.
>
> Another way is to make the behavior in 2 as the one in 5, that is to
> require one Tab in 2 and show "not unique" and completions at
> the same moment, it is the variant I prefer.
>
> A third, uber annoying way, is to make the behavior in 5 as the one in
> 2, that is to require two Tabs in 5, so going from ~/Desk to the
> completion menu for ~/Desktop would require three Tabs.
We are mis-communicating. Let's start from the beginning.
Scenario #1:
. User presses C-x C-f TAB
. Emacs says [Complete but not unique]
. User presses TAB once more
. Emacs pops up *Completions* and still says [Complete but not unique]
Scenario #2:
. User presses C-x C-f Desk TAB
. Emacs completes to ~/Desktop/
. User presses TAB once more
. Emacs pops up *Completions* and says [Complete but not unique]
The difference after the first TAB is because in Scenario #1 there's
nothing to complete, and what's in the minibuffer is already a valid
response to the prompt: it specifies an existing file/directory.
Whereas in Scenario #2 Emacs _can_ complete, and what the user typed
is not an existing file.
OK?
next prev parent reply other threads:[~2021-11-07 19:00 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 [this message]
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=83zgqf7pvm.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).