[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: "Final" version of tty child frames
From: |
martin rudalics |
Subject: |
Re: "Final" version of tty child frames |
Date: |
Wed, 11 Dec 2024 10:39:02 +0100 |
User-agent: |
Mozilla Thunderbird |
> There's something in the C code that makes this branch not work with
> the mini-frame package
> (https://github.com/muffinmad/emacs-mini-frame). The package works
> fine in graphical mode.
IIUC I use something similar to the mini-frame package and it's already
quite hairy to make the minibuffer frame pop up and automatically get
input focus. The input focus thing will be hard to implement on ttys.
> I'm using posframe for iteration. There's a minor thing where the
> cursor position is inconsistent when at the end of a line with a
> posframe on it in the tty. Maybe that's intentional? It's kinda
> confusing to me.
Is the cursor in the normal window or in the posframe window?
> There's also a major thing where I can click on the child frame in the
> tty and then my cursor is actually in the child frame and I can just
> alter the text there. That behavior is inconsistent with the behavior
> on graphical displays and something I can investigate.
Do you mean that you do _not_ want to alter text in the child frame?
If you have the time, please also try to look into two issues I raised
earlier:
Two further things I noticed: When point in the parent frame is
effectively hidden by the child frame, its cursor sometimes appears at
the right of the child frame and sometimes it's not shown. I have not
understood the underlying principle for this behavior. Also when the
selected region in the parent frame is active, its overlay covers the
child frame. That's ugly.
martin
Re: "Final" version of tty child frames,
martin rudalics <=