Re: A solution to display completion candidates after point in a minibuffer

[Stefan Monnier <monnier@iro.umontreal.ca>]

>> [ FWIW, I just tried it in my local Emacs where I replaced the ad-hoc
>> `resize_mini_window` scrolling with the use of `scroll-conservatively`,
>> and I get the behavior that you seem to prefer. ]
> Yes, that's not surprising, what your code does is essentially (or very
> close to) what I suggested to do in bug#43519 and bug#43572,

Not really, because with my code, the window start is not explicitly set
to BOB unless the buffer's content is small enough to be completely
visible (the first version of my patch did, but not the current one).

> Thank you, now I see what you mean.  IMO (and I would be extremely
> surprised if I were the only one with that opinion) seeing the current
> directory disappearing is disturbing (and from a newcomer point of
> view: very disturbing), so the prompt an user input should always be
> displayed (unless the miniwindow is too small of course).

I agree it's suboptimal when entering the minibuffer.  OTOH it's
a perfectly acceptable behavior while editing the minibuffer's content
and can even be preferable in some cases to what you propose.

>> IIRC the reason it won't scroll the second time around is because point
>> should be visible (and redisplay would only scroll in order to move point
>> within view).
> I don't know, but I'm not sure about that.  If you (set-window-start nil 1)
> unconditionally in window-scroll-functions, this setting will be obeyed by
> redisplay, even if point is not visible anymore.

Oh, indeed, in that case it would move point instead.


        Stefan