|
From: | Lennart Borgman (gmail) |
Subject: | Re: Display problems with 'before-string in overlay |
Date: | Sun, 15 Apr 2007 02:15:57 +0200 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.10) Gecko/20070221 Thunderbird/1.5.0.10 Mnenhy/0.7.5.666 |
Kim F. Storm wrote:
"Lennart Borgman (gmail)" <address@hidden> writes:Just another note if someone else is trying this. Having coming back to this several times today I am starting to believe that the way to fix this is to change cursor_row_p. This was the original way that Kim tried to solve it. Maybe Kim's solution with an added test of if the "string" has the 'display property will solve the problem for now. I am unable to test this now, since I do not understand how to check for the 'display property in cursor_row_p. If someone can tell that I will test.That is _not_ easy.You have to record that during redisplay (by display_line in the glyph row) if you need that information later.
But does not the code in set_cursor_from_row test for 'display in "strings"? Or is that another situation?
But I see now set_cursor_from_row just calls pos = XINT (Fnext_single_char_property_change (make_number (pos), Qdisplay, Qnil, limit));Can't that approach be used? glyph_row has a "pointer" to the position in the buffer through the field
display_pos start,where display_pos has a text_pos field. And text_pos has a charpos field, which I assume is the position in the buffer.
I am thinking about this solution since it seems rather safe to me.
[Prev in Thread] | Current Thread | [Next in Thread] |