all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 28236@debbugs.gnu.org, Ari Roponen <ari.roponen@gmail.com>,
	andrei.elkin@pp.inet.fi, dgutov@yandex.ru
Subject: bug#28236: 'configure --with-cairo' causes 'emacs -font' to fail
Date: Wed, 12 Dec 2018 16:41:52 +0100	[thread overview]
Message-ID: <m2tvji69bz.fsf@gmail.com> (raw)
In-Reply-To: <835zvy22t1.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 12 Dec 2018 17:16:26 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> So you are saying that the problem here is that Cairo can only work
> with fonts known fontconfig, and cannot switch to font backend(s) that
> bypass fontconfig?  If so, perhaps just an entry in PROBLEMS with the
> above recipe would suffice as a workaround?

I find that surprising. The non-Cairo GTK build can use Xft and X font
backends, what's different about Cairo?

(I just tried to set font-backend to '(ftcr x) on my Cairo build, and
failed, so perhaps it really isnʼt supported).

Robert





  reply	other threads:[~2018-12-12 15:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-25 19:57 bug#28236: 'configure --with-cairo' causes 'emacs -font' to fail andrei.elkin
2017-08-26  7:24 ` Eli Zaretskii
2018-12-11  1:50 ` Dmitry Gutov
2018-12-11  6:25   ` Eli Zaretskii
2018-12-12 12:03     ` Ari Roponen
2018-12-12 15:16       ` Eli Zaretskii
2018-12-12 15:41         ` Robert Pluim [this message]
2018-12-12 16:37           ` Eli Zaretskii
2018-12-13 11:34             ` Robert Pluim
2018-12-13 13:52               ` Eli Zaretskii
2018-12-13 14:56                 ` Robert Pluim
2019-06-04  7:47                   ` YAMAMOTO Mitsuharu
2019-06-08  5:13                     ` YAMAMOTO Mitsuharu

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2tvji69bz.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=28236@debbugs.gnu.org \
    --cc=andrei.elkin@pp.inet.fi \
    --cc=ari.roponen@gmail.com \
    --cc=dgutov@yandex.ru \
    --cc=eliz@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.