From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ismail@i10z.com, emacs-devel@gnu.org, raman@google.com
Subject: Re: Font problem on git master
Date: Mon, 20 Jan 2020 19:33:42 +0100 [thread overview]
Message-ID: <m24kwqrn95.fsf@gmail.com> (raw)
In-Reply-To: <831rruxcer.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 20 Jan 2020 19:31:24 +0200")
>>>>> On Mon, 20 Jan 2020 19:31:24 +0200, Eli Zaretskii <eliz@gnu.org> said:
>> Date: Mon, 20 Jan 2020 17:50:29 +0200
>> From: Eli Zaretskii <eliz@gnu.org>
>> Cc: ismail@i10z.com, rpluim@gmail.com, emacs-devel@gnu.org
>>
>> > From: "T.V Raman" <raman@google.com>
>> > Cc: İsmail Dönmez <ismail@i10z.com>,
>> > emacs-devel@gnu.org
>> > Date: Mon, 20 Jan 2020 07:27:52 -0800
>> >
>> > Could we update the News file with details on what font backends are
>> > now recommended?
>>
>> Indeed, I think we should.
Eli> Or maybe we could make Emacs ignore some font backend specifications
Eli> in .Xresources, when they conflict with the Cairo build? Would that
Eli> make sense?
Iʼm not sure that would have helped here. Weʼd have ended up using the
'x' backend, and I think the font in question was only available under
'xft', or 'ftcr' (or 'ftcrhb'). We could always complain, of course,
but that would also annoy people, no doubt.
Robert
next prev parent reply other threads:[~2020-01-20 18:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 10:20 Font problem on git master İsmail Dönmez
2020-01-20 10:39 ` Robert Pluim
2020-01-20 10:45 ` İsmail Dönmez
2020-01-20 11:00 ` Robert Pluim
2020-01-20 11:26 ` İsmail Dönmez
2020-01-20 12:38 ` Robert Pluim
2020-01-20 12:53 ` İsmail Dönmez
2020-01-20 13:52 ` Robert Pluim
2020-01-20 14:35 ` Robert Pluim
2020-01-20 15:27 ` T.V Raman
2020-01-20 15:50 ` Eli Zaretskii
2020-01-20 17:31 ` Eli Zaretskii
2020-01-20 18:33 ` Robert Pluim [this message]
2020-01-20 18:52 ` Eli Zaretskii
2020-01-20 16:21 ` Robert Pluim
2020-01-20 18:22 ` T.V Raman
2020-01-20 15:47 ` Eli Zaretskii
2020-01-20 16:34 ` Robert Pluim
2020-01-20 17:33 ` Eli Zaretskii
2020-01-20 18:05 ` İsmail Dönmez
2020-01-20 19:33 ` Andreas Schwab
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=m24kwqrn95.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ismail@i10z.com \
--cc=raman@google.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).