From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Robert Cochran <robert@cochranmail.com>,
shelvacu@gmail.com, 38569@debbugs.gnu.org,
robert-emacs@cochranmail.com
Subject: bug#38569: 27.0.50; Certain emoji crashes with "X protocol error: BadLength"
Date: Fri, 13 Dec 2019 10:01:16 +0100 [thread overview]
Message-ID: <m2y2vgvbtv.fsf@gmail.com> (raw)
In-Reply-To: <83r21890tf.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 13 Dec 2019 08:50:04 +0200")
>>>>> On Fri, 13 Dec 2019 08:50:04 +0200, Eli Zaretskii <eliz@gnu.org> said:
>> From: Robert Cochran <robert@cochranmail.com>
>> Date: Thu, 12 Dec 2019 13:34:46 -0800
>> Cc: Shelvacu <shelvacu@gmail.com>, 38569@debbugs.gnu.org,
>> Robert Cochran <robert-emacs@cochranmail.com>
>>
>> The easier thing is to add another exception to face-ignored-fonts, but
>> at this point it'd be a better idea to deal with it at the font renderer
>> level. IMO it's not scalable for the solution to be "ok, also add this
>> font to the exception list", especially as frequently as Emacs has
>> releases.
Eli> The problem is that AFAIR the "font renderer" that is to blame in this
Eli> case is XFT, and it doesn't seem to be actively maintained lately.
Eli> (Robert Pluim will correct me if I'm wrong.) That's why we are using
Eli> the face-ignored-fonts workaround.
Thatʼs correct. The real solution is 'stop using XFT', but I donʼt
think we can require cairo just yet, much as Iʼd like to do so.
Eli, we could install my patch to filter out all colour fonts (see
<https://lists.gnu.org/archive/html/bug-gnu-emacs/2019-11/msg00409.html>),
that should reduce the amount of whack-a-mole required.
Robert
next prev parent reply other threads:[~2019-12-13 9:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 23:41 bug#38569: 27.0.50; Certain emoji crashes with "X protocol error: BadLength" Robert Cochran
2019-12-12 8:50 ` Robert Pluim
2019-12-12 21:34 ` Robert Cochran
2019-12-13 6:50 ` Eli Zaretskii
2019-12-13 9:01 ` Robert Pluim [this message]
2019-12-13 9:14 ` Eli Zaretskii
2019-12-13 9:20 ` Eli Zaretskii
2019-12-13 9:43 ` Robert Pluim
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=m2y2vgvbtv.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=38569@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=robert-emacs@cochranmail.com \
--cc=robert@cochranmail.com \
--cc=shelvacu@gmail.com \
/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).