bug#43572: Feature request: make it possible to choose whether the first lines of the minibuffer should be displayed instead of the last ones

[Gregory Heytings]

> > > > I can't think of such unintended consequences.  In the use case of 
> > > > displaying completion candidates, this (the fact that it affects all 
> > > > successive calls to resize_mini_window) is indeed what is wanted.
> > >
> > > Well, I _can_ think of such consequences.  As I said, 
> > > resize_mini_window is called in many situations that don't involve 
> > > completion, so setting that variable to affect all of them is a bad 
> > > idea.  We need something more fine-grained if we want to implement 
> > > such a feature.
> >
> > It would be very helpful if you could clarify what the consequences you 
> > think of are.
>
> Just grep the sources for the callers of resize_mini_window, and you 
> will see what I mean.

I did this.  There are only seven calls to resize_mini_window().

> It is not safe to avoid affecting them using the techniques you propose.

Could you please provide a recipe which would demonstrate a problem with 
the technique I propose?  AFAICS, the flag is reset immediately when 
read_minibuf() / read-from-minibuffer has ended.