From: Eli Zaretskii <eliz@gnu.org>
To: Jeremy Van Cleve <jeremy.vancleve@gmail.com>,
Tassilo Horn <tsdh@gnu.org>
Cc: 61290@debbugs.gnu.org
Subject: bug#61290: 28.2; Ligatures messing up fontify subscripts in AUCTeX
Date: Sun, 05 Feb 2023 10:58:58 +0200 [thread overview]
Message-ID: <83pmaosd2l.fsf@gnu.org> (raw)
In-Reply-To: <A986EEF9-9B7F-46AB-A6B0-214C581A9BF6@gmail.com> (message from Jeremy Van Cleve on Sat, 4 Feb 2023 17:48:53 -0500)
> From: Jeremy Van Cleve <jeremy.vancleve@gmail.com>
> Date: Sat, 4 Feb 2023 17:48:53 -0500
>
> After loading emacs 28.2 with `emacs -Q` and installing AUCTeX, I enable
> ligatures (using FiraCode) and get the following fontify issues in a latex-mode:
>
> https://preview.redd.it/se7joc3h81ga1.png?width=1268&format=png&auto=webp&v=enabled&s=1322e80f7d7b0799858041dd1c9b4f44ea51fbb2
>
> Specifically, fontify is changing the font size correctly in the
> subscripts, but the baseline is not correct in a number of places
> include for + and * and when for x_{-}.
>
> Without the ligatures enabled, fontify renders the subscripts correctly:
>
> https://preview.redd.it/8g67r6lp81ga1.png?width=1358&format=png&auto=webp&v=enabled&s=3132a756de6a8266f8300e600b6d0dae94656ee9
Thanks.
My guess would be that the method used by AUCTeX for displaying
subscripts is somehow incompatible with character compositions. How
are subscripts displayed by AUCTeX?
OTOH, if this is a problem in the Emacs display engine, I'd appreciate
a simple reproducer that doesn't require AUCTeX to be installed and
used.
CC'ing Tassilo, in case he has some comments and idea.
next prev parent reply other threads:[~2023-02-05 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 22:48 bug#61290: 28.2; Ligatures messing up fontify subscripts in AUCTeX Jeremy Van Cleve
2023-02-05 8:58 ` Eli Zaretskii [this message]
2023-02-05 9:28 ` Tassilo Horn
2023-02-05 11:58 ` Eli Zaretskii
2023-02-12 12:16 ` Eli Zaretskii
2023-02-12 16:40 ` Jeremy Van Cleve
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=83pmaosd2l.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=61290@debbugs.gnu.org \
--cc=jeremy.vancleve@gmail.com \
--cc=tsdh@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).