Dov Feldstern wrote:
Stefan Schimanski wrote:
There's also a separate case, but it doesn't manifest itself in cursor
movement (in terms of affecting the number of keystrokes between
positions):
if I'm between emph and normal text, and type a character, should it be
emph or not? Well, if I'm coming from the emph to the border, then it
should be emph; and if I'm coming from the non-emph, it should be
non-emph.
Current behavior is not as it should be... I bet we can fix it using the
boundary...
I think that that's what the setCursorFont is supposed to be
doing. Same goes for languages. (Both situations are captured by the
"font" concept in LyX).
