bug#38645: 26.3; minibuffer input is called with multi-line window when multi-line message is shown

[martin rudalics]

>> But I'm too silly to understand why the minibuffer window does not
>> re-grow in the first place after having shown the result of C-x C-e.
>> Can you enlighten me?
>
> Re-grow upon which event?  If you do nothing, the message from "C-x C-e"
> stays displayed indefinitely.

Not here.  After a short pause I get the one line ?a back.

> If you mean why it doesn't re-grow upon some keystroke (which removes
> the message), I guess we are lacking a call to
> resize_echo_area_exactly in some place.

I guess so too.

> Regardless, I think keeping the prompt visible is a better behavior.

But while showing the result of C-x C-e (97 ...) it doesn't show any
prompt here, just an empty trailing line.  What am I missing?

> And yes, we should probably document this caveat, although I cannot
> imagine what application would like the current behavior.
>
>> martin, who just noted that the recently added (to master)
>>
>>         Lisp_Object str = build_string ("Command attempted to use minibuffer"
>>                                         "while in minibuffer");
>>
>> produces
>>
>> "Command attempted to use minibufferwhile in minibuffer"
>
> Hope you've already fixed it.

I cannot reliably push these days.  I have to first rebuild my git
environment and probably will wait with that until Glen has fixed the
copyright headers to avoid excessive re-compilations.  My machine is
getting a bit weak for so much work ...

martin