From: Yixuan Chen <xuan@xlk.me>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 73752@debbugs.gnu.org
Subject: bug#73752: 29.4; Ligatures are randomly rendered with extra spaces
Date: Sat, 12 Oct 2024 12:09:02 -0400 [thread overview]
Message-ID: <c068c0cd-9912-4291-99c5-9dcff8bdaf21@xlk.me> (raw)
In-Reply-To: <86zfn9ycis.fsf@gnu.org>
On 10/12/24 04:02, Eli Zaretskii wrote:
> I cannot reproduce the problem on my system. I've let Emacs randomize
> the fonts for quite some time, and everything keeps rendering
> correctly without the extra spaces. When you say "eventually", how
> long do you typically wait until the problem appears?
It took me 5 seconds at most, and usually happened immediately.
> (As two deviations from your init.el, I used a different font
> (Cascadia Code), since I don't have JetBrains Mono installed; and I
> replaces use-package with the equivalent Lisp, since I don't want to
> install ligatures.el on this system. I don't think these two
> deviations should matter, but I mention them FTR.)
I can replicate the same problem (and even worse in some cases) using
Cascadia Code.
The `use-package` should be replaceable, except you want to keep the
list of ligature strings formatted in the same way. I'm not fluent in
Elisp or emacs API, so my dumb way of randomization is achieved through
regexp matching over the ligature strings. If they are re-organized in
some way (say merged into one huge line), it might break the randomization.
> I think this might be system-dependent. Can someone try this in a
> Cairo build on GNU/Linux and see if the problem reproduces?
Potentially, I'm using emacs-pgtk on wayland.
next prev parent reply other threads:[~2024-10-12 16:09 UTC|newest]
Thread overview: 90+ 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 [this message]
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
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
2024-10-31 1:39 ` Tim Ruffing
2024-10-31 2:36 ` Yixuan Chen
2024-10-31 2:46 ` Yixuan Chen
2024-10-31 7:44 ` Eli Zaretskii
2024-10-31 9:42 ` Eli Zaretskii
2024-11-01 17:05 ` Eli Zaretskii
2024-11-02 3:34 ` Tim Ruffing
2024-11-02 9:52 ` Eli Zaretskii
2024-11-02 10:39 ` Visuwesh
2024-11-02 12:07 ` Eli Zaretskii
2024-11-02 13:29 ` Visuwesh
2024-11-02 16:47 ` Eli Zaretskii
2024-11-02 17:04 ` Visuwesh
2024-11-02 17:18 ` Eli Zaretskii
2024-11-02 17:31 ` Visuwesh
2024-11-02 17:34 ` Eli Zaretskii
2024-11-02 17:39 ` Visuwesh
2024-11-02 17:44 ` Eli Zaretskii
2024-11-02 17:54 ` Visuwesh
2024-11-02 18:02 ` Visuwesh
2024-11-02 18:27 ` Eli Zaretskii
2024-11-04 0:11 ` Tim Ruffing
2024-11-04 17:45 ` Eli Zaretskii
2024-11-04 18:02 ` Visuwesh
2024-11-04 23:33 ` Tim Ruffing
2024-11-04 23:47 ` Tim Ruffing
2024-11-06 12:02 ` Tim Ruffing
2024-11-06 13:11 ` Eli Zaretskii
2024-11-07 2:12 ` Tim Ruffing
2024-11-07 7:05 ` Eli Zaretskii
2024-11-07 13:45 ` Visuwesh
2024-11-07 14:40 ` Eli Zaretskii
2024-11-07 15:13 ` Visuwesh
2024-11-07 15:49 ` Eli Zaretskii
2024-11-07 16:00 ` Visuwesh
2024-11-08 8:08 ` Eli Zaretskii
2024-11-06 14:50 ` Visuwesh
2024-11-02 10:32 ` Visuwesh
2024-10-31 8:12 ` Visuwesh
2024-10-31 9:43 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c068c0cd-9912-4291-99c5-9dcff8bdaf21@xlk.me \
--to=xuan@xlk.me \
--cc=73752@debbugs.gnu.org \
--cc=eliz@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 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.