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 21:55:14 +0200	[thread overview]
Message-ID: <83v9137nbx.fsf@gnu.org> (raw)
In-Reply-To: <CAELgYhe6XvAWj0KHBWtohpAnWhV2aAc6XNpgA8xKKptw4yO7uQ@mail.gmail.com> (message from Carlos Pita on Sun, 7 Nov 2021 16:34:29 -0300)

> From: Carlos Pita <carlosjosepita@gmail.com>
> Date: Sun, 7 Nov 2021 16:34:29 -0300
> Cc: 51650@debbugs.gnu.org
> 
> So far so good, but I'm comparing the second Tab in scenario #2 to the
> first Tab in scenario #1 because they are both in states characterized
> by:
> 
> a. a valid response
> b. a non-unique completion
> c. no information yet communicated to the user about b

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.  And that's the reason for the difference in
behavior.





  reply	other threads:[~2021-11-07 19:55 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 [this message]
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=83v9137nbx.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).