From: Miles Bader <miles@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: another font-selection inconsistency
Date: Tue, 10 Jun 2008 20:48:34 +0900 [thread overview]
Message-ID: <buoskvljyst.fsf@dhapc248.dev.necel.com> (raw)
In-Reply-To: <buoabhtlehf.fsf@dhapc248.dev.necel.com> (Miles Bader's message of "Tue, 10 Jun 2008 20:24:28 +0900")
It seems to be the "foundry" info that makes the difference -- using
(set-face-attribute 'default nil :family "unknown-Dejavu Sans Mono"
:height 100) works "properly" even the first time.
A bit confusing, as I don't think most users think about the foundry much,
especially when there's only one font by that family name.
Here's what fc-list says btw:
$ env - HOME=/tmp fc-list 'Dejavu Sans Mono' file family foundry
/usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono.ttf: DejaVu Sans Mono:foundry=unknown
/usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono-BoldOblique.ttf: DejaVu Sans Mono:foundry=unknown
/usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono-Bold.ttf: DejaVu Sans Mono:foundry=unknown
/usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono-Oblique.ttf: DejaVu Sans Mono:foundry=unknown
$ env - HOME=/tmp fc-list 'Dejavu Sans Mono:foundry=unknown' file family foundry
/usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono.ttf: DejaVu Sans Mono:foundry=unknown
/usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono-BoldOblique.ttf: DejaVu Sans Mono:foundry=unknown
/usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono-Bold.ttf: DejaVu Sans Mono:foundry=unknown
/usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono-Oblique.ttf: DejaVu Sans Mono:foundry=unknown
$ env - HOME=/tmp fc-list 'Dejavu Sans Mono:foundry=dejavu' file family foundry
-Miles
--
Philosophy, n. A route of many roads leading from nowhere to nothing.
prev parent reply other threads:[~2008-06-10 11:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 11:24 another font-selection inconsistency Miles Bader
2008-06-10 11:40 ` Jason Rumney
2008-06-11 12:46 ` Kenichi Handa
2008-06-13 4:23 ` Kenichi Handa
2008-06-18 21:40 ` Stefan Monnier
2008-06-10 11:48 ` Miles Bader [this message]
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=buoskvljyst.fsf@dhapc248.dev.necel.com \
--to=miles@gnu.org \
--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).