From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 44020@debbugs.gnu.org, larsi@gnus.org, stephen.berman@gmx.net
Subject: bug#44020: 28.0.50; Prefer selection of colour emoji fonts?
Date: Tue, 20 Oct 2020 16:41:53 +0200 [thread overview]
Message-ID: <m2blgxc632.fsf@gmail.com> (raw)
In-Reply-To: <83ft69nf9d.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 20 Oct 2020 17:28:14 +0300")
>>>>> On Tue, 20 Oct 2020 17:28:14 +0300, Eli Zaretskii <eliz@gnu.org> said:
>> From: Robert Pluim <rpluim@gmail.com>
>> Cc: 44020@debbugs.gnu.org, larsi@gnus.org, Stephen Berman
>> <stephen.berman@gmx.net>
>> Date: Tue, 20 Oct 2020 10:58:31 +0200
>>
>> So it was failing on Debian as well, until I deleted my
>> ~/.config/fontconfig directory, which ended up fixing it on Ubuntu as
>> well.
Eli> This Fontconfig cache thingy appears in too many trouble reports.
Eli> Sounds like something we should ask users to do up front whenever they
Eli> report some weird font-related issue.
To be clear: this is not the fontconfig cache, itʼs the user-specific
directory for configuring fontconfig. I had one because I was playing
around with hinting styles at one point, and thatʼs exactly what can
cause Noto Color Emoji to fail (donʼt ask me why).
But yes, we should ask people to move both the fontconfig cache and
the fontconfig user directory out of the way (or ask them to run
FC_DEBUG=1024 emacs -Q, which will show us which fontconfig config
files are being loaded).
Robert
--
next prev parent reply other threads:[~2020-10-20 14:41 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 18:10 bug#44020: 28.0.50; Prefer selection of colour emoji fonts? Lars Ingebrigtsen
2020-10-15 18:52 ` Eli Zaretskii
2020-10-16 8:19 ` Robert Pluim
2020-10-16 10:26 ` Eli Zaretskii
2020-10-16 10:38 ` Robert Pluim
2020-10-16 10:49 ` Eli Zaretskii
2020-10-16 19:30 ` Alan Third
2020-10-17 6:38 ` Lars Ingebrigtsen
2020-10-17 9:12 ` Eli Zaretskii
2020-10-18 8:09 ` Lars Ingebrigtsen
2020-10-18 15:02 ` Eli Zaretskii
2020-10-19 8:35 ` Lars Ingebrigtsen
2020-10-17 15:27 ` Alan Third
2020-10-17 15:51 ` Alan Third
2020-10-17 6:44 ` Eli Zaretskii
2020-10-19 19:11 ` Robert Pluim
2020-10-16 14:49 ` Lars Ingebrigtsen
2020-10-19 10:56 ` Robert Pluim
2020-10-19 14:55 ` Eli Zaretskii
2020-10-19 18:34 ` Robert Pluim
2020-10-19 18:52 ` Eli Zaretskii
2020-10-19 19:00 ` Robert Pluim
2020-10-19 19:03 ` Stephen Berman
2020-10-19 19:46 ` Eli Zaretskii
2020-10-19 22:00 ` Stephen Berman
2020-10-20 2:35 ` Eli Zaretskii
2020-10-20 7:33 ` Robert Pluim
2020-10-20 8:58 ` Robert Pluim
2020-10-20 14:28 ` Eli Zaretskii
2020-10-20 14:41 ` Robert Pluim [this message]
2020-10-19 19:03 ` Stefan Kangas
2020-10-19 19:32 ` Robert Pluim
2020-10-19 19:47 ` Eli Zaretskii
2021-11-06 19:00 ` Lars Ingebrigtsen
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=m2blgxc632.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=44020@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=stephen.berman@gmx.net \
/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).