unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: "Patrick Lenihan [sc17pl]" <P.J.Lenihan1@leeds.ac.uk>
Cc: 51385@debbugs.gnu.org
Subject: bug#51385: 29.0.50; PragmataPro wide word ligatures such as [ERR] having the left side cut off in cairo build
Date: Wed, 27 Oct 2021 20:22:15 -0700	[thread overview]
Message-ID: <CADwFkmmHMtB=dgveVCk8qeOEKQRgdOyVsKAORy4n7hPaG9Syiw@mail.gmail.com> (raw)
In-Reply-To: <AM7PR03MB61513F4BFFA4048A54444F08DF839@AM7PR03MB6151.eurprd03.prod.outlook.com> (Patrick Lenihan's message of "Mon, 25 Oct 2021 11:52:00 +0000")

"Patrick Lenihan [sc17pl]" <P.J.Lenihan1@leeds.ac.uk> writes:

> When building Emacs with Cairo support, first characters are missing in
> many ligatures of PragmataPro. This issue has occurred since Emacs
> 27.1 but does not occur when building without Cairo. More details:
> https://github.com/fabrizioschiavi/pragmatapro/issues/181. The same
> occurs regardless of whether prettify-symbols or ligatures.el are
> used, although using ligatures.el appears to allow some of these
> characters to display correctly. More details on ligatures.el:
> https://github.com/mickeynp/ligature.el/issues/33.

Thanks for the bug report.

Could you provide a recipe to reproduce this issue, starting from
"emacs -Q"?





  reply	other threads:[~2021-10-28  3:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-25 11:52 bug#51385: 29.0.50; PragmataPro wide word ligatures such as [ERR] having the left side cut off in cairo build Patrick Lenihan [sc17pl]
2021-10-28  3:22 ` Stefan Kangas [this message]
     [not found]   ` <AM7PR03MB6151E876241AC93490E75926DF8B9@AM7PR03MB6151.eurprd03.prod.outlook.com>
2021-11-03 12:26     ` Patrick Lenihan [sc17pl]
2021-11-03 14:36       ` Eli Zaretskii
2021-11-03 15:08         ` Patrick Lenihan [sc17pl]
2021-11-03 17:17           ` Eli Zaretskii
2021-11-03 18:26             ` Patrick Lenihan [sc17pl]
2022-09-14 18:31               ` Lars Ingebrigtsen
2022-09-14 18:41                 ` 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='CADwFkmmHMtB=dgveVCk8qeOEKQRgdOyVsKAORy4n7hPaG9Syiw@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=51385@debbugs.gnu.org \
    --cc=P.J.Lenihan1@leeds.ac.uk \
    /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).