At 01:12 PM 4/24/2002 -0400, Charles Hines wrote:
>>>>> "Andy" == Andy Piper
Andy> This is on top of my previous patch. Chuck let me know if this doesn't
Andy> fix the problem you were seeing with VM.
Alrighty...doing that now...hm, I didn't try it with VM yet, but I see no
change in the behavior of my revamped simple testcase that mimics it...trying
VM now...yup, no change in the behavior (i.e. spaces between the strips are
still present in both VM and 'example-2' in my revamped testcase that I
included in my earlier email).
Ok, but in the case that you add the extent to a line *only* containing
"\n" rather than " \n" you should see a difference. I agree that
is the correct behavior if there is more text to display (a space in this
But then, as I said earlier, I'm still not sure that this new
actually an XEmacs redisplay bug. I mean, what if you had an extent that had
a small begin glyph but a lot of text in the extent and this text went past
the end of the screen, you'd expect that to wrap, correct? Assuming
It won't right now, I thought that implementing this was too big a behavior
change - since it would cause images to wrap also. Making them wrap is not
truncate-lines was set appropriately of course. I see no difference
the text in the extent is going beyond the end of the screen so it *should*
Right. It seems to me the most important case is that we don't just drop
text because it is inside an extent - it is the glyph we are clipping not
the extent itself.