From: Robert Pluim <rpluim@gmail.com>
To: tastytea <tastytea@tastytea.de>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>,
Pouar Dragon <pouar@pouar.net>,
43148@debbugs.gnu.org
Subject: bug#43148: 27.1; Widget text seems to disappear when building with Cairo and Xaw
Date: Fri, 04 Dec 2020 11:33:20 +0100 [thread overview]
Message-ID: <87eek5eu8f.fsf@gmail.com> (raw)
In-Reply-To: <20201204110905.06110be6@ventiloplattform.tastytea.de> (tastytea@tastytea.de's message of "Fri, 4 Dec 2020 11:09:05 +0100")
tastytea <tastytea@tastytea.de> writes:
>> If youʼre trying to say "I want to use Noto Color Emoji for emojis",
>> then I think you should write
>>
>> <family>emoji</family>
>
> That doesn't work, at least not in my terminal emulator.
>
You want emojis in your terminal emulator? I guess thereʼs no
accounting for taste :-)
>> not "serif" and "sans-serif", as Noto Color Emoji doesnʼt cover the
>> usual codepoints that are used for text.
>
> All the tutorials on the internet say to write it in "serif",
> "sans-serif" and "monospace". If the first font (Source Sans Pro in my
> case) doesn't cover the codepoint, the next font is used (Noto Color
> Emoji).
That surprises me, but then again this is fontconfig. Last time I
checked, Noto Color Emoji was already in the default fontconfig
settings, at least on Debian, so I wonder why you needed to have your
local settings.
Robert
next prev parent reply other threads:[~2020-12-04 10:33 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 2:21 bug#43147: 27.1; Widget text seems to disappear when building with Cairo and Xaw Pouar Dragon
2020-09-01 14:09 ` bug#43148: " Eli Zaretskii
2020-09-01 15:05 ` Robert Pluim
2020-09-01 15:51 ` Eli Zaretskii
2020-09-01 16:13 ` Robert Pluim
2020-09-01 16:48 ` Eli Zaretskii
2020-09-02 6:59 ` Robert Pluim
2020-09-02 10:24 ` James Cloos
2020-09-02 10:45 ` Robert Pluim
2020-09-02 14:05 ` Eli Zaretskii
2020-09-02 14:28 ` James Cloos
2020-09-02 14:50 ` Eli Zaretskii
2020-09-02 15:19 ` Robert Pluim
2020-09-02 15:25 ` Eli Zaretskii
2020-09-02 13:57 ` Eli Zaretskii
2020-09-02 11:38 ` Peder O. Klingenberg
2020-09-03 9:09 ` Robert Pluim
2020-09-03 9:18 ` Robert Pluim
2020-11-25 2:30 ` Basil L. Contovounesios
2020-11-28 8:22 ` YAMAMOTO Mitsuharu
2020-12-01 13:10 ` tastytea via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-03 2:13 ` YAMAMOTO Mitsuharu
2020-12-03 8:18 ` tastytea via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-04 8:41 ` YAMAMOTO Mitsuharu
2020-12-04 9:28 ` tastytea via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-04 9:48 ` Robert Pluim
2020-12-04 10:09 ` tastytea via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-04 10:33 ` Robert Pluim [this message]
2020-12-04 10:58 ` tastytea via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-04 11:46 ` Robert Pluim
2020-12-04 12:14 ` tastytea via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-05 6:51 ` YAMAMOTO Mitsuharu
2020-12-05 7:14 ` tastytea via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-06 5:26 ` YAMAMOTO Mitsuharu
2020-12-06 5:58 ` Eli Zaretskii
2020-09-02 2:15 ` YAMAMOTO Mitsuharu
2020-09-28 10:46 ` Pouar Dragon
2020-11-23 17:38 ` 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=87eek5eu8f.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=43148@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=pouar@pouar.net \
--cc=tastytea@tastytea.de \
/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).