From: Eli Zaretskii <eliz@gnu.org>
To: Vin Shelton <acs@alumni.princeton.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Font issues with recent emacs
Date: Thu, 09 Jan 2014 08:49:10 +0200 [thread overview]
Message-ID: <83bnzlejkp.fsf@gnu.org> (raw)
In-Reply-To: <CACeGjnUuw=JkZemnFVnq=G_FGiKP-HsAHenL=MYOZG+yN0TrJg@mail.gmail.com>
> Date: Wed, 8 Jan 2014 22:13:47 -0500
> From: Vin Shelton <acs@alumni.princeton.edu>
>
> 1. xlsfonts shows the font exists:
>
> xlsfonts -fn "-*-dejavu sans mono-medium-r-normal--12-*-*-*-m-*-iso8859-1"
> -misc-dejavu sans mono-medium-r-normal--12-87-100-100-m-0-iso8859-1
>
> 2. Then I start the emacs using that font as the default:
> emacs -Q -fn "-misc-dejavu sans
> mono-medium-r-normal--12-87-100-100-m-0-iso8859-1"
>
> 3. emacs starts with the modeline as displayed in the attached
> modeline.png. Notice that the buffer name '*scratch* ' is spelled out
> in ascii blocks.
The buffer name uses the bold variant of the font. If the font you
specified doesn't have a bold variant, Emacs will not be able to
display it.
> Similarly, if I invoke emacs and evaluate the following forms in the
> *scratch* buffer:
>
> emacs -Q
> (set-face-font 'default "-*-dejavu sans
> mono-medium-r-normal--12-*-*-*-m-*-iso8859-1")
> (set-face-font 'mode-line "-microsoft-comic sans
> ms-medium-r-normal-*-12-*-*-*-*-*-iso8859-1")
>
> The default font changes correctly and the modeline displays
> correctly, but if I enter info:
> C-h i
>
> Then the top of the *info* (dir) buffer looks like the attached
> info.png. Note the same ascii block characters.
Again, because that part of the display needs the italics variant of
the font.
Why do you insist on forcing on Emacs a specific fully qualified font
definition?
next prev parent reply other threads:[~2014-01-09 6:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 3:13 Font issues with recent emacs Vin Shelton
2014-01-09 6:49 ` Eli Zaretskii [this message]
2014-01-09 18:26 ` Vin Shelton
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=83bnzlejkp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acs@alumni.princeton.edu \
--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).