From: Geoffrey Alan Washburn <geoffw@cis.upenn.edu>
Subject: Re: unicode-2 branch segfaulting on MacOS X?
Date: Fri, 27 Oct 2006 09:36:31 -0400 [thread overview]
Message-ID: <45420B5F.3000006@cis.upenn.edu> (raw)
In-Reply-To: <E1GdMIW-0005ZY-00@etlken>
Kenichi Handa wrote:
>
> Hmmm, this means that your "bitstream vera sans mono" font
> doesn't have FC_WIDTH property. Very strange. What does
> this command return?
>
> % fc-list 'bitstream vera sans mon' width
Strange, it just returned a blank line. After deleting the Bitstream
fontconfig cache file and rebuilding with "sudo fc-cache", this fixed
problems as far as fc-list was concerned.
% fc-list fc-list 'bitstream vera sans mono' width
:width=100
However, emacs is still reporting that it is getting an empty string for
the width property. That is, your new error message
peculiar error: "invalid font property", (:width . "")
next prev parent reply other threads:[~2006-10-27 13:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-22 15:36 unicode-2 branch segfaulting on MacOS X? Geoffrey Alan Washburn
2006-10-23 1:04 ` Kenichi Handa
2006-10-23 1:17 ` Geoffrey Alan Washburn
2006-10-23 2:45 ` Kenichi Handa
2006-10-23 3:32 ` Geoffrey Alan Washburn
2006-10-23 5:59 ` Kenichi Handa
2006-10-23 10:00 ` Geoffrey Alan Washburn
2006-10-23 11:26 ` Kenichi Handa
2006-10-23 12:55 ` Geoffrey Alan Washburn
2006-10-27 4:17 ` Kenichi Handa
2006-10-27 10:05 ` Geoffrey Alan Washburn
2006-10-27 7:38 ` Kenichi Handa
2006-10-27 13:36 ` Geoffrey Alan Washburn [this message]
2006-10-28 0:41 ` Giorgos Keramidas
2006-10-28 0:43 ` Giorgos Keramidas
2006-10-28 17:39 ` Geoffrey Alan Washburn
2006-11-03 16:43 ` Geoffrey Alan Washburn
2006-11-08 11:55 ` Kenichi Handa
2006-11-08 19:23 ` Geoffrey Alan Washburn
2006-11-09 3:20 ` stephen
2006-11-09 11:41 ` Kenichi Handa
2006-11-12 2:59 ` Geoffrey Alan Washburn
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=45420B5F.3000006@cis.upenn.edu \
--to=geoffw@cis.upenn.edu \
/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).