unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 15:55:33 +0300	[thread overview]
Message-ID: <86jzex8ddm.fsf@gnu.org> (raw)
In-Reply-To: <dcsfrplnvxj.fsf@sdf.org> (message from Van Ly on Fri, 27 Sep 2024 12:05:44 +0000)

> From: Van Ly <van.ly@sdf.org>
> Cc: 73511@debbugs.gnu.org
> Date: Fri, 27 Sep 2024 12:05:44 +0000
> 
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > 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.
> >
> 
> On reaching the point in the path /usr/src/external/gpl highlighting
> either gpl2 or gpl3 in the only 1 *Completions* window and pressing C-j
> will enter dired mode for that directory.
> 
> Pressing TAB at that point on either highlighted alternatives duplicates
> the *Completions* window resulting in 2 *Completions* windows.  And, as
> far as I know the user has to mouse select from the duplicated window.

No, you can select with C-j or with M-TAB.

> The intended behavior is to get to the target configure file preferably
> without needing to mouse point in the second *Completions* window, TAB
> would select from the inferred highlighted option.

No, in Icomplete mode TAB does not select.  I suggest to read the
"Icomplete" node in the Emacs user manual, it explains how to use this
mode.





  reply	other threads:[~2024-09-27 12:55 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
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 [this message]
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=86jzex8ddm.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).