From: Steve Purcell <steve@sanityinc.com>
To: David Leatherman <leathekd@gmail.com>
Cc: alptekin.aker@gmail.com, 11450@debbugs.gnu.org
Subject: bug#11450: 24.1.50; NS regression: fallback font used even when glyph available in primary font
Date: Wed, 5 Sep 2012 14:38:50 +0100 [thread overview]
Message-ID: <04B0147D-5C8A-4111-A4E3-3C03FA5BC849@sanityinc.com> (raw)
In-Reply-To: <m2627sk8gc.fsf@leathekd.com>
Hah! I think I made progress. I believe the commit to which you (David) referred is basically helpful, in that it more correctly catalogues the various character ranges.
On a whim, I tried adding a "set-fontset-font" call to my usual font setup, as shown below:
(set-fontset-font "fontset-default" 'symbol "PragmataPro")
(set-face-attribute 'default nil :foundry "apple" :family "PragmataPro" :height 140)
And that actually causes Emacs to use the default font for both the "GREEK SMALL LETTER LAMDA" and "EMPTY SET" characters.
I guess that in the absence of this line, Emacs asks the system for a font which supports the "symbol" character range, without first trying the default font.
As for why Menlo works like this out of the box and the other fonts don't, that's still a mystery to me.
-Steve
next prev parent reply other threads:[~2012-09-05 13:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 12:45 bug#11450: 24.1.50; NS regression: fallback font used even when glyph available in primary font Steve Purcell
2012-05-11 16:10 ` Alp Aker
[not found] ` <9AC1B178-DAD0-4757-B477-65BAB21A6991@sanityinc.com>
2012-05-11 20:43 ` Alp Aker
2012-05-13 10:25 ` Steve Purcell
2012-05-14 8:39 ` Steve Purcell
2012-05-15 23:33 ` Alp Aker
2012-08-15 1:23 ` David Leatherman
2012-09-04 19:09 ` David Leatherman
2012-09-05 9:38 ` Steve Purcell
2012-09-05 11:36 ` David Leatherman
2012-09-05 13:38 ` Steve Purcell [this message]
2012-09-06 1:13 ` David Leatherman
2012-09-06 7:21 ` Steve Purcell
2016-07-17 20:41 ` Alan Third
2016-07-17 22:54 ` Steve Purcell
2016-07-19 14:41 ` David Leatherman
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=04B0147D-5C8A-4111-A4E3-3C03FA5BC849@sanityinc.com \
--to=steve@sanityinc.com \
--cc=11450@debbugs.gnu.org \
--cc=alptekin.aker@gmail.com \
--cc=leathekd@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).