From: Eli Zaretskii <eliz@gnu.org>
To: Van Ly <van.ly@sdf.org>
Cc: 73511@debbugs.gnu.org
Subject: bug#73511: 30.0.91; icomplete-vertical-mode TAB-key pops two completions windows
Date: Fri, 27 Sep 2024 13:35:33 +0300 [thread overview]
Message-ID: <86msjt8juy.fsf@gnu.org> (raw)
In-Reply-To: <dcssetlv8ze.fsf@sdf.org> (bug-gnu-emacs@gnu.org)
> Date: Fri, 27 Sep 2024 07:41:57 +0000
> From: Van Ly via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> 1. open "emacs -Q"
> 2. M-x icomplete-vertical-mode
> 3. navigate with TAB completions after find-file C-x C-f
>
> Say, I want to open the following using find-file C-x C-f
>
> /usr/src/external/gpl3/gcc/dist/gcc/configure
>
> The directory /usr/src/external has two subdirectories gpl2 and gpl3.
>
> at the point /usr/src/ex TAB completes the path to /usr/src/external/
>
> at the point /usr/src/external/gp TAB completes the path to /usr/src/external/gpl
>
> at the point /usr/src/external/gpl
>
> C-n or C-p will move the highlight between gpl2 or gpl3 (See A)
>
> pressing TAB pops a second *Completions* window (See B)
>
> Expected behavior is for TAB to pick the highlighted directory and continue with path to file selection
>
> => http://sdf.org/~van.ly/img/emacs-30-0-91-pretest-icomplete-vertical-mode-buffer-A.jpeg A
> => http://sdf.org/~van.ly/img/emacs-30-0-91-pretest-icomplete-vertical-mode-buffer-B.jpeg B
There are no 2 *Completions* windows. Instead, you have one
*Completions* window and the list of completions in the mini-window.
I think this is the intended behavior, and see no bug here.
next prev parent reply other threads:[~2024-09-27 10:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 7:41 bug#73511: 30.0.91; icomplete-vertical-mode TAB-key pops two completions windows Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-27 10:35 ` Eli Zaretskii [this message]
2024-09-27 12:05 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-27 12:55 ` Eli Zaretskii
2024-09-27 17:58 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-12 11:19 ` 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=86msjt8juy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=73511@debbugs.gnu.org \
--cc=van.ly@sdf.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).