bug#45474: Icomplete exhibiting in recursive minibuffer when it shouldn’t

[Gregory Heytings]

> > > >    run_hook (Qminibuffer_setup_hook);
> > >
> > > As in my patch, you could use this hook to do the completion-specific 
> > > part of the setup.
> >
> > Indeed, but you said that 'minibuffer-with-setup-hook' is 
> > "fundamentally broken and messy"...
>
> I forgot to add that if the idea is to change the semantics of 
> read-from-minibuffer in the long term, this must happen inside 
> read-from-minibuffer, not with a minibuffer-with-setup-hook around 
> read-from-minibuffer.  What would be possible here (I think) is to move 
> this piece of code in a minibuffer-with-setup-hook inside the 
> read-from-minibuffer macro.

And here is the patch which does this, in case you prefer it.  AFAICS it 
is functionally equivalent to the other one.

Make-it-possible-to-disable-a-completion-backend-in-.patch
Description: Text Data