From: Visuwesh <visuweshm@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, 73752@debbugs.gnu.org, xuan@xlk.me
Subject: bug#73752: 29.4; Ligatures are randomly rendered with extra spaces
Date: Wed, 30 Oct 2024 11:13:21 +0530 [thread overview]
Message-ID: <87msimywli.fsf@gmail.com> (raw)
In-Reply-To: <867c9q6bx0.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 29 Oct 2024 19:45:15 +0200")
[செவ்வாய் அக்டோபர் 29, 2024] Eli Zaretskii wrote:
>> Thank you very much for the clear instructions. I was testing this in a
>> fresh Emacs session. And
>>
>> (gdb) pp composition_gstring_from_id(ID)
>>
>> seems to show nothing?
>>
>> (gdb) c
>> Continuing.
>>
>> Thread 1 "emacs" hit Breakpoint 3, set_cursor_from_row (w=0x55b8c994f338, row=0x55b8c9e20410, matrix=0x55b8c9960480, delta=0, delta_bytes=0, dy=0, dvpos=0) at xdisp.c:18217
>> 18217 struct glyph *glyph = row->glyphs[TEXT_AREA];
>> (gdb) pgrow
>> TEXT: 4 glyphs
>> 0 0: COMP[16 (0..0)] pos=5 w=9 a+d=14+4 face=28 MB
>> 1 9: COMP[16 (1..1)] pos=6 w=9 a+d=14+4 face=28 MB
>> 2 18: COMP[16 (2..2)] pos=7 w=9 a+d=14+4 face=28 MB
>> 3 27: CHAR[ ] pos=0 blev=0,btyp=B w=9 a+d=14+4 MB
>> (gdb) pp composition_gstring_from_id(16)
>> (gdb) p composition_gstring_from_id(16)
>> $1 = XIL(0x55b8cada607d)
>>
>> Am I missing something?
>
> Maybe your Emacs is not built with enough debug info?
I built a debug version of Emacs specifically for this.
./configure --with-sound=alsa --with-x-toolkit=lucid --without-xaw3d \
--without-gconf --without-libsystemd --with-cairo \
--enable-checking='yes,glyphs' \
--enable-check-lisp-object-type CFLAGS='-O0 -g3'
> What does this produce:
>
> (gdb) p composition_gstring_from_id(16)
> $1 = XIL(0x55b8cada607d)
> (gdb) xpr
>
> If this doesn't work, either, you will have to decypher
> XIL(0x55b8cada607d) "by hand", using xvector etc... I can give you
> instructions for that as well.
(gdb) p composition_gstring_from_id(16)
$3 = XIL(0x55b8cada607d)
(gdb) xpr
Lisp_Vectorlike
PVEC_NORMAL_VECTOR
$4 = (struct Lisp_Vector *) 0x55b8cada6078
{XIL(0x55b8cada60ad), make_fixnum(16), XIL(0x55b8cada60d5), XIL(0x55b8cada612d), XIL(0x55b8cada6185)}
So I am guessing we do need to decypher it "by hand"?
next prev parent reply other threads:[~2024-10-30 5:43 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 16:18 bug#73752: 29.4; Ligatures are randomly rendered with extra spaces xuan
2024-10-12 8:02 ` Eli Zaretskii
2024-10-12 16:09 ` Yixuan Chen
2024-10-27 10:21 ` Eli Zaretskii
2024-10-27 16:19 ` Visuwesh
2024-10-27 17:19 ` Eli Zaretskii
2024-10-27 17:27 ` Eli Zaretskii
2024-10-27 17:39 ` Yixuan Chen
2024-10-27 17:43 ` Eli Zaretskii
2024-10-27 17:46 ` Yixuan Chen
2024-10-27 19:14 ` Eli Zaretskii
2024-10-27 19:36 ` Yixuan Chen
2024-10-27 19:44 ` Eli Zaretskii
2024-10-27 19:47 ` Yixuan Chen
2024-10-27 20:11 ` Eli Zaretskii
2024-10-27 19:41 ` Yixuan Chen
2024-10-27 20:07 ` Eli Zaretskii
2024-10-27 20:32 ` Yixuan Chen
2024-10-28 14:25 ` Eli Zaretskii
2024-10-28 14:44 ` Yixuan Chen
2024-10-28 14:47 ` Yixuan Chen
2024-10-28 15:05 ` Eli Zaretskii
2024-10-28 15:20 ` Yixuan Chen
2024-10-28 17:19 ` Eli Zaretskii
2024-10-28 17:26 ` Eli Zaretskii
2024-10-28 17:28 ` Yixuan Chen
2024-10-28 18:41 ` Eli Zaretskii
2024-10-28 4:26 ` Visuwesh
2024-10-28 14:59 ` Eli Zaretskii
2024-10-28 15:24 ` Yixuan Chen
2024-10-28 16:18 ` Visuwesh
2024-10-28 17:13 ` Eli Zaretskii
2024-10-29 10:59 ` Visuwesh
2024-10-29 13:04 ` Eli Zaretskii
2024-10-29 13:54 ` Visuwesh
2024-10-29 14:00 ` Visuwesh
2024-10-29 15:38 ` Eli Zaretskii
2024-10-29 16:46 ` Visuwesh
2024-10-29 17:45 ` Eli Zaretskii
2024-10-30 5:43 ` Visuwesh [this message]
2024-10-29 16:51 ` Eli Zaretskii
2024-10-27 17:29 ` Yixuan Chen
2024-10-29 23:14 ` Tim Ruffing
2024-10-30 15:12 ` Eli Zaretskii
2024-10-30 15:45 ` Eli Zaretskii
[not found] ` <mvmikt9zkcq.fsf@suse.de>
2024-10-30 15:47 ` Eli Zaretskii
2024-10-30 17:34 ` Tim Ruffing
2024-10-30 17:46 ` Eli Zaretskii
2024-10-30 18:00 ` Tim Ruffing
2024-10-30 18:57 ` Eli Zaretskii
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=87msimywli.fsf@gmail.com \
--to=visuweshm@gmail.com \
--cc=73752@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=xuan@xlk.me \
/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).