unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: bad default font on Windows mingw64
Date: Mon, 22 Jul 2019 12:13:59 -0700	[thread overview]
Message-ID: <86tvbd6fwo.fsf@stephe-leake.org> (raw)
In-Reply-To: <8336iyq81l.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 22 Jul 2019 20:43:34 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Stephen Leake <stephen_leake@stephe-leake.org>
>> Date: Mon, 22 Jul 2019 10:02:03 -0700
>> 
>> With recent builds of master on mingw64, I'm getting a missing default
>> font; see attached screenshot of emacs -Q.

> But you can invoke Emacs in
> a way that instructs it to use Uniscribe instead:
>
>   emacs -Q -xrm Emacs.fontBackend:uniscribe

That gives me a readable font. But my normal startup complains:

    Font `Courier-9' is not defined

One of my normal startup commands changes the font to "Courier-9", via
`modify-frame-parameters'. Apparently that works with harfbuzz, but not
Uniscribe.

> If you click S-mouse-2 and select "Change Buffer Font...", what font
> is shown in the dialog as the current one?

I assume that's the font that is selected when the dialog starts.

With the Uniscribe backend, it's "Courier New". "Courier" does not show
size 9.

Same for harbuzz backend.

In harbuzz, if I use that dialog to select 'fixedsys', the buffer is
readable; the minibuffer and mode bar are not. Same for "Courier", but
that does.

Selecting "Lucida Console" or "Courier New" give unreadable fonts.

-- 
-- Stephe



  reply	other threads:[~2019-07-22 19:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-22 17:02 bad default font on Windows mingw64 Stephen Leake
2019-07-22 17:43 ` Eli Zaretskii
2019-07-22 19:13   ` Stephen Leake [this message]
2019-07-22 19:35     ` Eli Zaretskii
2019-07-22 22:10       ` Stephen Leake
2019-07-22 22:58         ` Óscar Fuentes
2019-07-23  1:03           ` Stephen Leake
2019-07-23  2:37             ` Eli Zaretskii
2019-07-25 16:51               ` Eli Zaretskii

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=86tvbd6fwo.fsf@stephe-leake.org \
    --to=stephen_leake@stephe-leake.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).