[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#74617: 30.0.92; ffap-menu always displays the *Completions* buffer
From: |
Eli Zaretskii |
Subject: |
bug#74617: 30.0.92; ffap-menu always displays the *Completions* buffer |
Date: |
Sun, 01 Dec 2024 08:17:31 +0200 |
> From: Drew Adams <drew.adams@oracle.com>
> CC: Eli Zaretskii <eliz@gnu.org>,
> "74617@debbugs.gnu.org"
> <74617@debbugs.gnu.org>,
> "monnier@iro.umontreal.ca"
> <monnier@iro.umontreal.ca>
> Date: Sat, 30 Nov 2024 21:30:35 +0000
>
> > > The pattern where completion commands want to display candidates
> > > immediately is not uncommon. There are ffap, tmm and multiple
> > > third-party packages which have such a requirement. So I suggest to not
> > > necessarily treat "immediate candidate display" as a bug report, but
> > > rather as a feature request for `completing-read'.
> >
> > And imenu.el calls minibuffer-completion-help conditionally
> > unless imenu-eager-completion-buffer is not nil.
>
> `minibuffer-completion-help' is above all a user
> command.
>
> Why should any code call `minibuffer-completion-help',
> other than code in minibuffer.el, or code in a command
> whose purpose is (at least partly) to show *Completions*?
We are talking here about a command that explicitly wants to show
*Completions*.
- bug#74617: 30.0.92; ffap-menu always displays the *Completions* buffer,
Eli Zaretskii <=