unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <Stephen.Berman@gmx.net>
To: emacs-devel@gnu.org
Subject: Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)
Date: Thu, 20 Dec 2007 11:29:48 +0100	[thread overview]
Message-ID: <87ir2tpskj.fsf@escher.local.home> (raw)
In-Reply-To: E1J59fr-0000Va-7n@etlken.m17n.org

On Thu, 20 Dec 2007 09:54:07 +0900 Kenichi Handa <handa@ni.aist.go.jp> wrote:

> In article <874peeu3yd.fsf@escher.local.home>, Stephen Berman <Stephen.Berman@gmx.net> writes:
>
>> I just did an update from the unicode-2 branch and built with make
>> bootstrap successfully.  But when I start Emacs with -Q, no frame opens
>> and the shell returns this message: peculiar error: "invalid font
>> property", (:weight . r)
>
> It seems that the parsing of XLFD failed.
>
> [...]
>> Lisp Backtrace:
>> "font-spec" (0xbfbfaaa4)
>> "apply" (0xbfbfab88)
>> "x-complement-fontset-spec" (0xbfbfacd4)
>> "create-fontset-from-fontset-spec" (0xbfbfae14)
>> "create-fontset-from-x-resource" (0xbfbfaf54)
>
> Please show me how you set X resource for fontsets.

I don't have set X resources in my home directory.  I'm running KDE
using the gtk-qt engine for GTK apps, and in my personal settings for
this engine I have the option "Use my KDE fonts in GTK applications"
set, but I'm afraid I don't know how they are set.  As a test I created
~/.Xresources with a setting for Emacs.font, ran xrdb on it and then
invoked unicode Emacs, but it still just returned the peculiar error
message (Emacs from CVS trunk did use that font, so I know it is valid).
Can you tell me what I should do to make sure a certain font is set for
unicode Emacs from outside of Emacs?

Steve Berman

  reply	other threads:[~2007-12-20 10:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-19 14:58 23.0.60; peculiar error: "invalid font property", (:weight . r) Stephen Berman
2007-12-19 15:24 ` Jason Rumney
2007-12-19 15:32   ` Stephen Berman
2007-12-20  0:58   ` Kenichi Handa
2007-12-20  0:54 ` Kenichi Handa
2007-12-20 10:29   ` Stephen Berman [this message]
2007-12-20 11:21     ` Andreas Schwab
2007-12-20 14:14       ` Stephen Berman
2007-12-21  0:47         ` Kenichi Handa
2007-12-21 16:40           ` Stephen Berman
2007-12-23 18:40             ` hcz
2007-12-26  0:57             ` Kenichi Handa
2008-01-03 20:18               ` Attn. Andreas Schwab (was Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)) Stephen Berman
2008-01-03 22:07                 ` Andreas Schwab
2008-01-03 23:03                   ` Attn. Andreas Schwab Stephen Berman
2007-12-20 10:54   ` 23.0.60; peculiar error: "invalid font property", (:weight . r) KOBAYASHI Yasuhiro
2007-12-20 12:42     ` Kenichi Handa
2007-12-20 14:14       ` Stephen Berman
2007-12-21 16:27       ` KOBAYASHI Yasuhiro
2007-12-26  1:56         ` Kenichi Handa
2007-12-26 15:47           ` KOBAYASHI Yasuhiro
2008-01-17  5:16             ` KOBAYASHI Yasuhiro

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=87ir2tpskj.fsf@escher.local.home \
    --to=stephen.berman@gmx.net \
    --cc=emacs-devel@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 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).