From: Eli Zaretskii <eliz@gnu.org>
To: Anand Tamariya <atamariya@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Incorrect glyph info in describe-char
Date: Fri, 23 Jul 2021 13:25:58 +0300 [thread overview]
Message-ID: <83tukl1g3t.fsf@gnu.org> (raw)
In-Reply-To: <CADm7Y4mOO1EEwQkvy3Cad4WE++8WKoDbK9-4NZuZvmrqKO8GzA@mail.gmail.com> (message from Anand Tamariya on Fri, 23 Jul 2021 13:45:23 +0530)
> From: Anand Tamariya <atamariya@gmail.com>
> Date: Fri, 23 Jul 2021 13:45:23 +0530
> Cc: emacs-devel@gnu.org
>
> My bad. I mixed up the test. After applying the text property on SHIN, the result is:
> (10 13 [[#<font-object "-PfEd-DejaVu Sans-bold-oblique-normal-*-78-*-*-*-*-0-iso10646-1"> 1513 1473
> 1464] 63 [0 2 1464 1305 0 8 35 0 17 nil] [0 2 1473 1314 0 63 73 56 -48 nil] [0 2 1513 1344 58 6 67 43 0 nil]])
Ah. So the problem is somewhere inside find_automatic_composition or
the functions it calls. If you can step through that code with GDB,
please do (I'll provide instructions if you need them). Failing that,
someone who can reproduce the problem would need to see what happens
in there; I cannot reproduce the issue with the fonts I have here.
prev parent reply other threads:[~2021-07-23 10:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 7:02 Incorrect glyph info in describe-char Anand Tamariya
2021-07-22 7:18 ` Eli Zaretskii
2021-07-22 8:03 ` Anand Tamariya
2021-07-22 8:54 ` Eli Zaretskii
2021-07-22 9:12 ` Anand Tamariya
2021-07-22 10:06 ` Eli Zaretskii
2021-07-22 11:27 ` Eli Zaretskii
2021-07-23 5:03 ` Anand Tamariya
2021-07-23 5:52 ` Eli Zaretskii
2021-07-23 6:28 ` Eli Zaretskii
2021-07-23 6:41 ` Anand Tamariya
2021-07-23 6:58 ` Eli Zaretskii
2021-07-23 7:36 ` Anand Tamariya
2021-07-23 7:45 ` Eli Zaretskii
2021-07-23 8:15 ` Anand Tamariya
2021-07-23 10:25 ` Eli Zaretskii [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83tukl1g3t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=atamariya@gmail.com \
--cc=emacs-devel@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).