From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 50c5d56: --with-cairo is no longer experimental
Date: Thu, 07 Nov 2019 16:31:34 +0200 [thread overview]
Message-ID: <838sorg3ll.fsf@gnu.org> (raw)
In-Reply-To: <m2pni4vzqc.fsf@gmail.com> (message from Robert Pluim on Thu, 07 Nov 2019 09:48:27 +0100)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org
> Date: Thu, 07 Nov 2019 09:48:27 +0100
>
> Eli> If the problem is a single font (or a small number of known fonts), we
> Eli> could disable them through face-ignored-fonts, conditioned on the
> Eli> right symbols that identify the problematic build(s). Does that make
> Eli> sense?
>
> It makes sense, but unfortunately the GTK font widget code doesnʼt
> check face-ignored-fonts, so weʼd have to hoist that code out of
> font_list_entities.
Just making GTK font selection take face-ignored-fonts into account
sounds like a nice improvement to me, almost a bugfix. So if this is
not too tricky to implement, I think we should go this way.
Thanks.
next prev parent reply other threads:[~2019-11-07 14:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190619070851.22726.77187@vcs0.savannah.gnu.org>
[not found] ` <20190619070853.E841E208EC@vcs0.savannah.gnu.org>
2019-11-05 10:33 ` [Emacs-diffs] master 50c5d56: --with-cairo is no longer experimental Robert Pluim
2019-11-05 18:25 ` Eli Zaretskii
2019-11-05 20:07 ` Robert Pluim
2019-11-06 3:34 ` Eli Zaretskii
2019-11-06 7:39 ` Robert Pluim
2019-11-06 16:11 ` Eli Zaretskii
2019-11-07 8:48 ` Robert Pluim
2019-11-07 14:31 ` Eli Zaretskii [this message]
2019-11-07 16:11 ` Robert Pluim
2019-11-07 17:24 ` Eli Zaretskii
2019-11-08 21:40 ` Robert Pluim
2019-11-08 22:59 ` Paul Eggert
2019-11-12 7:47 ` Robert Pluim
2019-11-12 13:32 ` Stefan Monnier
2019-11-09 6:44 ` Eli Zaretskii
2019-11-12 7:51 ` Robert Pluim
2019-11-14 9:48 ` Robert Pluim
2019-11-14 14:10 ` Eli Zaretskii
2019-11-14 11:53 ` Eli Zaretskii
2019-11-14 12:21 ` 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=838sorg3ll.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=rpluim@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).