From: Kenichi Handa <handa@m17n.org>
To: Bernhard Herzog <bernhard.herzog@intevation.de>
Cc: 6618@debbugs.gnu.org
Subject: bug#6618: Bug was probably introduced by revision 100788
Date: Wed, 14 Jul 2010 13:01:51 +0900 [thread overview]
Message-ID: <tl7aapu3e4w.fsf@m17n.org> (raw)
In-Reply-To: <201007131239.08209.bernhard.herzog@intevation.de> (message from Bernhard Herzog on Tue, 13 Jul 2010 12:39:08 +0200)
In article <201007131239.08209.bernhard.herzog@intevation.de>, Bernhard Herzog <bernhard.herzog@intevation.de> writes:
> I'm running into the same problem and I've debugged it a little. AFAICT the
> problem was introduced with revision 100788. The revision immediately before
> that works fine, but I can observer the problem with revision 100788. The
> ChangeLog entry for this is
> 2010-07-12 Kenichi Handa <handa@m17n.org>
> * font.h (enum font_property_index): New member FONT_ENTITY_INDEX.
> * font.c (font_open_entity): Record ENTITY in FONT_OBJECT's slot
> of FONT_ENTITY_INDEX.
> (Ffont_get): If KEY is :otf and the font-object doesn't have the
> property, get the property value dynamically.
> (Ffont_put): Accept font-entity and font-object too.
> (Ffont_get_glyhphs): Renamed from Fget_font_glyphs. Arguments and
> return value changed.
> (syms_of_font): Adjusted for the above change.
> It's most likely the first change in font.c: "Record ENTITY in FONT_OBJECT's
> slot of FONT_ENTITY_INDEX.":
Thank you for finding that problem. The reason of recording
ENTITY in FONT-OBJECT is that we can get :otf property only
from FONT-OBJECT, but the property should be common to all
font-ojbects realized from the same ENTITY. So, I wanted a
way to get ENTITY from FONT-OBJECT. I've just committed a
change to cancel that recording.
As a result, we should re-caliculate :otf property of a font
whose sibling (i.e. a font-object realized from the same
entity but with different size) already know it. But,
perhaps, that doesn't influence the redisplay speed that
match.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2010-07-14 4:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 11:01 bug#6618: 24.0.50; stack overflow in equal john ffitch
2010-07-13 10:39 ` bug#6618: Bug was probably introduced by revision 100788 Bernhard Herzog
2010-07-14 4:01 ` Kenichi Handa [this message]
2010-07-16 8:38 ` bug#6618: 24.0.50; stack overflow in equal john ffitch
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=tl7aapu3e4w.fsf@m17n.org \
--to=handa@m17n.org \
--cc=6618@debbugs.gnu.org \
--cc=bernhard.herzog@intevation.de \
/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.