Re: Question about minibuffer and child frames (Posframe)

[Gerd Möllmann]

Feng Shu <tumashu@163.com> writes:

> Gerd Möllmann <gerd.moellmann@gmail.com> writes:
>
>> martin rudalics <rudalics@gmx.at> writes:
>>
>>>> In that case it looks indeed as if there is some minimum height/width
>>>> requirement, although I can't it see in the code right now. I've made me
>>>> a todo item for this. Thanks!
>>>
>>> The minimum height of the minibuffer window is one frame line with
>>> IGNORE t in
>>>
>>> (window-min-size (minibuffer-window) nil t)
>>>
>>> and (due to a bug, see Bug#73022) 'window-min-height' with IGNORE nil.
>>>
>>> You have to make a minibuffer-less child frame to get less.
>>>
>>> martin
>>
>> Feng Shu made a posframe in his example with posframe-show which
>> presumably has no minibuffer. At least that was the fix for my Corfu and
>> Posframes being 1 line too large. This seems to be something ddifferent.
>
> if string >= 3 lines, posframe-show works well too, have problem when <
> 3 line.

Could be this in frame_windows_min_size:

  /* Don't allow too small height of text-mode frames, or else cm.c
     might abort in cmcheckmagic.  */
  if ((FRAME_TERMCAP_P (f) || FRAME_MSDOS_P (f)) && NILP (horizontal))
    {
      int min_height = (FRAME_MENU_BAR_LINES (f)
                        + FRAME_TAB_BAR_LINES (f)
                        + FRAME_WANTS_MODELINE_P (f)
                        + 2);   /* one text line and one echo-area line */

--------------------------^^^

      if (retval < min_height)
        retval = min_height;
    }

Must find out something else firwt though. With master pulled today
C-x o errors with "no next window". But of course not with -q and not
right from the beginning but caused by something unknown 👀.