unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 10:24:33 +0200	[thread overview]
Message-ID: <838ry09xvi.fsf@gnu.org> (raw)
In-Reply-To: <CAELgYhcX4aefed-XUQtE44W79zukJzXdqxrMSd+Wkq=h1Zusdg@mail.gmail.com> (message from Carlos Pita on Sun, 7 Nov 2021 05:16:50 -0300)

> From: Carlos Pita <carlosjosepita@gmail.com>
> Date: Sun, 7 Nov 2021 05:16:50 -0300
> Cc: 51650@debbugs.gnu.org
> 
> I can understand why things work the way they do by looking at the
> implementation. But I can't put it into simple meaningful reasons. The
> manual says that when Tab is unable to complete it displays a list of
> possible completions, yet in step 2 this is not true.

That's because TAB _is_ able to complete, but only partially.  And
with file names, it can well be that the partial match is what you
want.

> The implementation checks that the last command and the current
> command are the same before showing that list of completions, so it
> surely won't happen in step 2 since it's the first and only Tab in
> the sequence. In order to explain this, one seems forced to say that
> _at least_ two Tabs in a row have to be pressed to show the
> *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.





  reply	other threads:[~2021-11-07  8:24 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 [this message]
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

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=838ry09xvi.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).