From: Kenichi Handa <handa@m17n.org>
To: Dan Nicolaescu <dann@gnu.org>
Cc: 10233@debbugs.gnu.org
Subject: bug#10233: Font is not defined error at startup
Date: Thu, 08 Dec 2011 11:39:06 +0900 [thread overview]
Message-ID: <tl71usf948l.fsf@m17n.org> (raw)
In-Reply-To: <yxqipltvk0e.fsf@fencepost.gnu.org> (message from Dan Nicolaescu on Tue, 06 Dec 2011 09:42:57 -0500)
In article <yxqipltvk0e.fsf@fencepost.gnu.org>, Dan Nicolaescu <dann@gnu.org> writes:
> When starting up the current trunk I get this error:
> Font `-b&h-lucidatypewriter-medium-r-normal-sans-12-120-75-75-m-70-iso10646-1'
> is not defined
> That font is set in .Xdefaults, and it has not changed in years.
> The cause is this checkin:
> 106614: Kenichi Handa 2011-12-05 [merge] ftfont.c (get_adstyle_property): If the font is not BDF nor PCF, return Qnil
Oops, sorry, I made a silly mistake. I've just installed
the attached change. Please try again. If it still doesn't
fix your problem, please let me know the value of fcstr
after the call of FcPatternGetString (p, FC_FONTFORMAT, 0,
&fcstr) in the change.
---
Kenichi Handa
handa@m17n.org
=== modified file 'src/ftfont.c'
--- src/ftfont.c 2011-12-05 07:48:29 +0000
+++ src/ftfont.c 2011-12-08 02:30:40 +0000
@@ -166,8 +166,8 @@
#ifdef FC_FONTFORMAT
if ((FcPatternGetString (p, FC_FONTFORMAT, 0, &fcstr) == FcResultMatch)
- && (xstrcasecmp ((char *) fcstr, "bdf") != 0
- || xstrcasecmp ((char *) fcstr, "pcf") != 0))
+ && xstrcasecmp ((char *) fcstr, "bdf") != 0
+ && xstrcasecmp ((char *) fcstr, "pcf") != 0)
/* Not a BDF nor PCF font. */
return Qnil;
#endif
next prev parent reply other threads:[~2011-12-08 2:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 14:42 bug#10233: Font is not defined error at startup Dan Nicolaescu
2011-12-08 2:39 ` Kenichi Handa [this message]
2011-12-08 7:35 ` Dan Nicolaescu
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=tl71usf948l.fsf@m17n.org \
--to=handa@m17n.org \
--cc=10233@debbugs.gnu.org \
--cc=dann@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.