Re: Question about minibuffer and child frames (Posframe)

[martin rudalics]

> I have a question about minibuffer handling with child frames. Actually,
> it's something that currently behaves differently on GUI and tty with
> Posframe, via Vertico-Posframe, plus consult-buffer and similar. Since
> I've looked at this for two hours today without being able to tell what
> I'm missing here, I thought I'd just ask if you, or anyone else, has an
> idea where to look.
>
> Here's what I see:
>
> On GUI, consult-buffer pops up a child frame, which has, AFAICT, a
> minibuffer at the top. The cursor is in that minibuffer. The minibuffer
> ih the parent frame looks inactive. There is no prompt or anything else.
> That's how it should be.
>
> With my new code on tty, the same child frame pops up, but this time the
> child frame's minibuffer contains a prompt and what I type is displayed
> there and so on, but it doesn't have a visible cursor. The parent
> frame's minibuffer this time contains the prompt and the cursor, too.
>
> Any idea what that could be?

Remember what I asked earlier?

> >> Looks good.  But where does the user's answer appear?  In the
> >> child-frame's minibuffer window?
> >
> > If you mean the 'y' when I type y at the prompt, that appears just after
> > the prompt, that should be the echo area I think.
>
> Good.  I asked because I didn't see the cursor in the minibuffer window.
> But screenshots often don't capture cursors.

Cursor handling on ttys is an arcane art as I recently noticed.  I have
no idea how it works.  Does the echo area work normally when you are in
the child frame in the sense that text does not appear in the normal
minibuffer frame too?  Does the cursor show up as expected in normal
text areas when you switch between parent and child frame?  If so, I see
no way around tracing cursor movement during a dialogue and look where
the cursor_to commands come from.  Also the fact that the prompt appears
in both minibuffer windows is obviously fishy but IMHO it's a redisplay
issue as well.

Maybe as a first step I would not give child frames on ttys their own
minibuffer windows.  Let them use the minibuffer window of the normal
frame that hosts them and you're done (making sure that a child frame
never obscures a minibuffer window).  User input always goes to the same
terminal window so there are no focusing or redirecting issues you have
to resolve.  And displaying dialogues from minibuffer-less child frames
should be handled correctly anyway.

martin