From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail
From: Eli Zaretskii <eliz@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Re: Font problem on git master
Date: Mon, 20 Jan 2020 20:52:44 +0200
Message-ID: <83r1zuvu2r.fsf@gnu.org>
References: <CAMAzfThm4m5z6s-gpOi==Fcs4FTZA67VEN=QQ-0qJySatjBDCA@mail.gmail.com>
 <m2a76itnry.fsf@gmail.com>
 <CAMAzfThdq70u3sFHLHK05=MfXz2ykzvo0vVW1-MFQrDXP5y9+A@mail.gmail.com>
 <m25zh6tmse.fsf@gmail.com>
 <CAMAzfTg9yEO3dbSSuxXC1vFFESfQY5qA=9cgH5MGMMNYSeiWig@mail.gmail.com>
 <m21rruti8z.fsf@gmail.com>
 <CAMAzfTjgMc1FcDjiTJeewhgiCcPjXafwxCaG7C5t65u=Fz_JCQ@mail.gmail.com>
 <m2wo9ms09p.fsf@gmail.com> <m2sgkary9s.fsf@gmail.com>
 <p91h80qkv0n.fsf@google.com> <83a76ixh2y.fsf@gnu.org>
 <831rruxcer.fsf@gnu.org> <m24kwqrn95.fsf@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202";
	logging-data="124958"; mail-complaints-to="usenet@ciao.gmane.io"
Cc: ismail@i10z.com, raman@google.com, emacs-devel@gnu.org
To: Robert Pluim <rpluim@gmail.com>
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Jan 20 19:53:29 2020
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>
Envelope-to: ged-emacs-devel@m.gmane-mx.org
Original-Received: from lists.gnu.org ([209.51.188.17])
	by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>)
	id 1itcAy-000WRU-J0
	for ged-emacs-devel@m.gmane-mx.org; Mon, 20 Jan 2020 19:53:28 +0100
Original-Received: from localhost ([::1]:42948 helo=lists1p.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.90_1)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>)
	id 1itcAx-0002HO-J9
	for ged-emacs-devel@m.gmane-mx.org; Mon, 20 Jan 2020 13:53:27 -0500
Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60446)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <eliz@gnu.org>) id 1itcA9-0001IP-7c
 for emacs-devel@gnu.org; Mon, 20 Jan 2020 13:52:38 -0500
Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:58579)
 by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from <eliz@gnu.org>)
 id 1itcA8-0006vB-LE; Mon, 20 Jan 2020 13:52:36 -0500
Original-Received: from [176.228.60.248] (port=2112 helo=home-c4e4a596f7)
 by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256)
 (Exim 4.82) (envelope-from <eliz@gnu.org>)
 id 1itcA8-0007c6-3X; Mon, 20 Jan 2020 13:52:36 -0500
In-reply-to: <m24kwqrn95.fsf@gmail.com> (message from Robert Pluim on Mon, 20
 Jan 2020 19:33:42 +0100)
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=subscribe>
Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org
Original-Sender: "Emacs-devel"
 <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>
Xref: news.gmane.io gmane.emacs.devel:244437
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/244437>

> From: Robert Pluim <rpluim@gmail.com>
> Date: Mon, 20 Jan 2020 19:33:42 +0100
> Cc: ismail@i10z.com, emacs-devel@gnu.org, raman@google.com
> 
>     >> > 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.

Then NEWS it is, I guess.

Thanks.