Andre Poenitz wrote:
On Wed, Oct 03, 2007 at 01:20:42PM +0100, John Levon wrote:
On Wed, Oct 03, 2007 at 08:25:12AM +0200, Abdelrazak Younes wrote:
However, insets imply all sorts of things about cursor movement and
mouse placement. Unless things in this area got *massively* cleaned up
since I last looked at the code, getting correct cursor movement with
char-ranges-as-insets will not be easy.
We will face challenge for sure but Cursor movement is already working
well for entering and leaving insets. We will have to decide what to do
That's true for the current insets, absolutely *not* for char styles.
It's not acceptable for it to need two keypresses to get from a to b in
'ab' just because a has a different char style.
Well. And I want two _explicit_ cursor positions there, independent of
the implementation...
See my suggestion elsewhere that there should be an Invisible geometry
for charstyles. In that case, the cursor would ignore the boundary: if
the boundaries of the inset are invisible to the user, then they should
be invisible to the cursor. If, on the other hand, the inset boundaries
are drawn---via corners, or whatever---then you get the additional
boundaries. And (on the other note), you may have two, three, or four,
and the insets may all have different displays, making for maximum
flexibility.
Richard
Andre'
