GNU bug report logs - #3452
23.0.94; display

Previous Next

Package: emacs;

Reported by: rms <at> gnu.org

Date: Wed, 3 Jun 2009 03:00:03 UTC

Severity: serious

Done: Chong Yidong <cyd <at> stupidchicken.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Chong Yidong <cyd <at> stupidchicken.com>
Cc: 3452 <at> debbugs.gnu.org, handa <at> m17n.org
Subject: bug#3452: 23.0.94; display
Date: Sun, 07 Jun 2009 10:30:20 -0400
> From: Chong Yidong <cyd <at> stupidchicken.com>
> Cc: 3452 <at> emacsbugs.donarmstrong.com,  handa <at> m17n.org
> Date: Sun, 07 Jun 2009 09:56:05 -0400
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > Btw, I don't understand how these characters are related to
> > compositions.  They should not be composed with anything, they always
> > stand for themselves.
> 
> I didn't know that.  This means there is a bug in either
> find_composition (called from composition_compute_stop_pos) or
> next_element_from_composition (called from next_element_from_buffer),
> because the following code in next_element_from_buffer (xdisp.c:6519) is
> triggered for this character:
> 
>   if (CHAR_COMPOSED_P (it, IT_CHARPOS (*it), IT_BYTEPOS (*it))
>       && next_element_from_composition (it))
>     {
>        return 1;
>     }

I hope Handa-san could shed some light on this issue.




This bug report was last modified 15 years and 153 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.