Subject: Re: bug#74617: 30.0.92; ffap-menu always displays the *Completions* buffer

From: Eli Zaretskii <[email-masked]>
Date: Sat, 30 Nov 2024 18:59:20 +0200

> From: Daniel Mendler <[email-masked]>
> Cc: [email-masked],  [email-masked]
> Date: Sat, 30 Nov 2024 17:25:07 +0100
> 
> Eli Zaretskii <[email-masked]> writes:
> 
> >> I see it differently. The problem is in the tmm and ffap commands which
> >> lead to a mixture of completion UIs. Even if another completion UI is in
> >> effect, the default completion UI is called by tmm and ffap, bypassing
> >> the `completing-read' abstraction.
> >
> > I don't understand: ffap-menu calls completing-read, so what
> > abstraction does it bypass, and how?
> 
> It also calls `minibuffer-completion-help' which belongs to the default
> completion UI but not strictly to the abstract `completing-read' API.

So the problem is this single line?

      (let ((minibuffer-setup-hook 'minibuffer-completion-help))