From: Eli Zaretskii <eliz@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 3452@emacsbugs.donarmstrong.com
Subject: bug#3452: 23.0.94; display
Date: Sun, 07 Jun 2009 10:30:20 -0400 [thread overview]
Message-ID: <E1MDJO8-0004yP-Et@fencepost.gnu.org> (raw)
In-Reply-To: <87r5xwgnbe.fsf@cyd.mit.edu> (message from Chong Yidong on Sun, 07 Jun 2009 09:56:05 -0400)
> From: Chong Yidong <cyd@stupidchicken.com>
> Cc: 3452@emacsbugs.donarmstrong.com, handa@m17n.org
> Date: Sun, 07 Jun 2009 09:56:05 -0400
>
> Eli Zaretskii <eliz@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.
next prev parent reply other threads:[~2009-06-07 14:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-07 3:47 bug#3452: 23.0.94; display Chong Yidong
2009-06-07 9:16 ` Eli Zaretskii
2009-06-07 13:56 ` Chong Yidong
2009-06-07 14:30 ` Eli Zaretskii [this message]
2009-06-07 20:41 ` Chong Yidong
2009-06-07 22:53 ` Eli Zaretskii
2009-06-08 1:51 ` Kenichi Handa
2009-06-08 4:48 ` Eli Zaretskii
2009-06-08 8:10 ` Kenichi Handa
2009-06-08 8:44 ` Eli Zaretskii
2009-06-08 11:57 ` Kenichi Handa
2009-06-08 14:47 ` Chong Yidong
2009-06-09 18:00 ` Chong Yidong
2009-06-10 0:35 ` Kenichi Handa
-- strict thread matches above, loose matches on Subject: below --
2009-06-06 2:48 Chong Yidong
2009-06-03 2:53 Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1MDJO8-0004yP-Et@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=3452@emacsbugs.donarmstrong.com \
--cc=cyd@stupidchicken.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.