unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>, jpff <jpff@codemist.co.uk>
Cc: emacs-devel@gnu.org
Subject: Re: FC_COLOR in src/ftfont.c
Date: Tue, 3 Apr 2018 08:17:08 -0700	[thread overview]
Message-ID: <31f38510-46c0-c14b-ea2e-1f98a03d0536@cs.ucla.edu> (raw)
In-Reply-To: <8360585r3c.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 452 bytes --]

On 04/03/2018 06:58 AM, Eli Zaretskii wrote:
> I guess the solution depends on whether systems with fontconfig that
> doesn't support FC_COLOR are still susceptible to the original bug.

I doubt whether they're susceptible. Even if they are, we're better off 
compiling Emacs on such systems rather than having the build fail; at 
least that way we can further debug the problem. So I installed the 
attached workaround to help move the ball forward.


[-- Attachment #2: 0001-Port-FC_COLOR-change-to-older-fontconfig.txt --]
[-- Type: text/plain, Size: 1099 bytes --]

From 0f923ac2629c819cb16860d154945485e48287cb Mon Sep 17 00:00:00 2001
From: Paul Eggert <eggert@cs.ucla.edu>
Date: Tue, 3 Apr 2018 08:12:41 -0700
Subject: [PATCH] Port FC_COLOR change to older fontconfig
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Problem reported by John ff in:
https://lists.gnu.org/r/emacs-devel/2018-04/msg00058.html
* src/ftfont.c (ftfont_spec_pattern) [!FC_COLOR]:
Don’t use FC_COLOR on older fontconfigs that don’t have it.
---
 src/ftfont.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/ftfont.c b/src/ftfont.c
index 24a92dd52e..84e4a30389 100644
--- a/src/ftfont.c
+++ b/src/ftfont.c
@@ -764,7 +764,7 @@ ftfont_spec_pattern (Lisp_Object spec, char *otlayout, struct OpenTypeSpec **ots
   if (scalable >= 0
       && ! FcPatternAddBool (pattern, FC_SCALABLE, scalable ? FcTrue : FcFalse))
     goto err;
-#ifdef HAVE_XFT
+#if defined HAVE_XFT && defined FC_COLOR
   /* We really don't like color fonts, they cause Xft crashes.  See
      Bug#30874.  */
   if (Vxft_ignore_color_fonts
-- 
2.14.3


  parent reply	other threads:[~2018-04-03 15:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-03 13:05 FC_COLOR in src/ftfont.c jpff
2018-04-03 13:58 ` Eli Zaretskii
2018-04-03 15:15   ` jpff
2018-04-03 15:17   ` Paul Eggert [this message]
2018-04-03 15:46     ` 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=31f38510-46c0-c14b-ea2e-1f98a03d0536@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jpff@codemist.co.uk \
    /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).