[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: xdisp.c problem?
From: |
Tak Ota |
Subject: |
Re: xdisp.c problem? |
Date: |
Fri, 31 Jan 2003 09:34:08 -0800 (PST) |
Fri, 31 Jan 2003 12:58:37 +0900 (JST): Kenichi Handa <address@hidden> wrote:
> It seems that Fnext_single_char_property_change is called
> with POS == 0 in this code:
>
> L9525: pos = make_number (string_buffer_position (w, glyph->object,
> L9526: string_before_pos));
> L9527: pos = Fnext_single_char_property_change (pos, Qdisplay, Qnil,
> limit);
>
> That means string_buffer_position returns 0 in your case.
>
> Hmmm, as this function checks only `display' property, that
> is a likely result if the buffer contains overlay string.
>
> I've just installed the attached patch to skip such glyphs
> that come from overlay string. Please try again.
I've just tested the patch already applied xdips.c from the CVS this
morning. It works fine now, even on this inferior system too. Thank
you.
-Tak
- Re: xdisp.c problem?, (continued)
- Re: xdisp.c problem?, Kenichi Handa, 2003/01/29
- Re: xdisp.c problem?, Tak Ota, 2003/01/29
- Re: xdisp.c problem?, Kenichi Handa, 2003/01/29
- Re: xdisp.c problem?, Tak Ota, 2003/01/30
- Re: xdisp.c problem?, Tak Ota, 2003/01/30
- Re: xdisp.c problem?, Tak Ota, 2003/01/30
- Re: xdisp.c problem?, Kenichi Handa, 2003/01/30
- Re: xdisp.c problem?, Masatake YAMATO, 2003/01/30
- Re: xdisp.c problem?, Kenichi Handa, 2003/01/31
- Re: xdisp.c problem?, Masatake YAMATO, 2003/01/31
- Re: xdisp.c problem?,
Tak Ota <=
- Re: xdisp.c problem?, Richard Stallman, 2003/01/31
- Re: xdisp.c problem?, Masatake YAMATO, 2003/01/30
- Re: xdisp.c problem?, Tak Ota, 2003/01/30
- Re: xdisp.c problem?, Masatake YAMATO, 2003/01/30