Re: "Final" version of tty child frames

[Gerd Möllmann]

Jared Finder <jared@finder.org> writes:

> The good news is that this seems to affect both xterm as well as Linux
> terminals, so hopefully someone more familiar with this code can
> debug.  A simple repro case (with posframe installed):
>
> 1. Evaluate (posframe-show " *test*" :string (concat "A\nB\n*long
> text*\nC\nD"))
> 2. Now try to place the cursor on some text after one of the single
> letter lines while still being in the root frame. (I've been using M-x
> info since the directory node has lots of nice text)

I can't yet reproduce this. I do this

  (posframe-show " *test*" :string (concat "A\nB\n*long text*\nC\nD")
     :background-color "grey15")

That pops up the posframe. Then I C-h i d to display the Info dir in the
root frame. The posframe is still there of course. Only one window on
the root frame.
 
> When I do this, my cursor always appears at the end of the line so
> long as it is after the posframe.  When the cursor is before the
> posframe, the cursor is displayed fine.

I move point in the root frame, in the Info dir buffer. When it is under
the posframe, my bar cursor is not shown, when I move right, it appears
when it is no longer under the posframe, when I move left again it
disappears. I've done that for the lines of the posframe, but I don't
see the cursor behaving strangely.

This is on macOS, iTerm2, TERM=xterm-256color.

So, something is still missing in the recipe, I guess. Or I'm missing
something when trying to reproduce this. Could you perhaps try with -Q
and without posframe?

> I confirmed via debugging code that tty_cursor_to and
> tty_raw_cursor_to were being called with the expected values, so the
> cursor must be moving after that.
>
>   -- MJF