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 22:38:56 +0200 [thread overview]
Message-ID: <83r1br7lb3.fsf@gnu.org> (raw)
In-Reply-To: <CAELgYherabwPqhpsfo9sNRbmmVrppyZv9+iBkU+Q72Z3U-kwtg@mail.gmail.com> (message from Carlos Pita on Sun, 7 Nov 2021 17:27:58 -0300)
> From: Carlos Pita <carlosjosepita@gmail.com>
> Date: Sun, 7 Nov 2021 17:27:58 -0300
> Cc: 51650@debbugs.gnu.org
>
> > But the difference is that until the first TAB the user cannot know
> > whether there is any completion. Only after Emacs doesn't complete is
> > that fact known.
>
> First of all, I'm assuming:
>
> - The initial value is taken from the current working directory so
> it's always a valid completion.
The completion doesn't know that. It's just what the caller arranged
for it to display.
> - TAB never completes across the directory boundary.
But it can complete less than that.
> You seem to be saying that the TAB that produced ~/Desktop/ from
> ~/Desk is adding some worthy information about the contents of
> ~/Desktop, and therefore about possible completions, that
> wouldn't be there if the user, say, launched emacs from ~/Desktop
> as in #3. But, for the life of me, I cannot see it :(
The completion doesn't know where it was launched from. It just knows
what the user typed, and in the "~/" case the user didn't type
anything.
next prev parent reply other threads:[~2021-11-07 20:38 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 [this message]
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=83r1br7lb3.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).