From: "T.V Raman" <raman@google.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: "İsmail Dönmez" <ismail@i10z.com>, emacs-devel@gnu.org
Subject: Re: Font problem on git master
Date: Mon, 20 Jan 2020 07:27:52 -0800 [thread overview]
Message-ID: <p91h80qkv0n.fsf@google.com> (raw)
In-Reply-To: <m2sgkary9s.fsf@gmail.com> (Robert Pluim's message of "Mon, 20 Jan 2020 15:35:43 +0100")
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 1523 bytes --]
Robert Pluim <rpluim@gmail.com> writes:
I ran into a similar issue over the weekend after building emacs from
Git.
I had inherited these lines in .Xresources from way back:
Emacs.FontBackend: ftcrhb,xft,x
Emacs*font: -adobe-Utopia-normal-normal-normal-*-*-*-*-*-*-0-iso10646-1
After the update/build, emacs refused to start in GUI mode, -- emacs -nw
worked, and it displayed the font backend error when started as emacs
under X.
I worked around the problem by commenting out the emacs.font line and it
started with Adobe Courier.
This morning, I updated the font backend line as suggested by you, and
now I get over 3,000+ fonts -- and uncommenting the Adobe Utopia line
does not cause the error.
Could we update the News file with details on what font backends are
now recommended?
>>>>>> On Mon, 20 Jan 2020 14:52:34 +0100, Robert Pluim <rpluim@gmail.com> said:
> Robert> If all else fails, can you run 'strace emacs' with your normal config
> Robert> to see if it0¶3s loading some site-specific configuration files? Those
> Robert> might be messing with the font setup.
>
> In fact, looking through Andreas' package repo, I see it includes an
> app-defaults.Emacs that does:
>
> Emacs.FontBackend: xft,x
>
> which is going to cause problems on a cairo-enabled build. Is it
> possible for you to remove that setting, or try something like
>
> Emacs.FontBackend: ftcrhb,xft,x
>
> or
>
> Emacs.FontBackend: ftcrhb,x
>
>
> Robert
>
--
next prev parent reply other threads:[~2020-01-20 15:27 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 [this message]
2020-01-20 15:50 ` Eli Zaretskii
2020-01-20 17:31 ` Eli Zaretskii
2020-01-20 18:33 ` Robert Pluim
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=p91h80qkv0n.fsf@google.com \
--to=raman@google.com \
--cc=emacs-devel@gnu.org \
--cc=ismail@i10z.com \
--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).