From: Robert Pluim <rpluim@gmail.com>
To: VanL <van@scratch.space>
Cc: help-gnu-emacs@gnu.org
Subject: Re: 26.3, 28; Set Default Font... CMU Typewriter Text
Date: Mon, 27 Jan 2020 15:24:22 +0100 [thread overview]
Message-ID: <m2a7697zah.fsf@gmail.com> (raw)
In-Reply-To: <m2o8up3v3g.fsf@scratch.space> (VanL's message of "Tue, 28 Jan 2020 00:08:35 +1100")
>>>>> On Tue, 28 Jan 2020 00:08:35 +1100, VanL <van@scratch.space> said:
VanL> Robert Pluim <rpluim@gmail.com> writes:
>> >> Emacs.FontBackend: ftcrhb,x
>>
VanL> Emacs.FontBackend: ftcrhb,xft,x
>>
VanL> Emacs must use FreeType as the above JustWorks™ for the
VanL> context its in.
>>
>> Why are you messing with Emacs.FontBackend? I canʼt think of any
>> reason why you should need to set that explicitly rather than letting
>> Emacs work it out by itself.
VanL> The creepy crawly spidery font that occurs in Emacs-28 between quote
VanL> marks, by default, was something I lived with to the moment it was
VanL> raised in a thread on emacs-devel. Then on, I followed the discussion
VanL> on fonts to improve that setting. And, pieced together the info that
VanL> is at the head of this thread. Another discomfort I live with is a
VanL> long delay when I first open a file with a mix of CJ asia east fonts.
OK, but that has nothing to do with FontBackend. If the default font
is not to your liking, you can change it easily enough.
The delay I think is inevitable when Emacs has to search through lots
of fonts.
Robert
next prev parent reply other threads:[~2020-01-27 14:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 9:43 26.3, 28; Set Default Font... CMU Typewriter Text VanL
2020-01-25 6:10 ` VanL
2020-01-26 20:04 ` Robert Pluim
2020-01-27 13:08 ` VanL
2020-01-27 14:24 ` Robert Pluim [this message]
2020-01-27 15:31 ` VanL
2020-01-27 15:59 ` Robert Pluim
2020-01-27 17:50 ` VanL
2020-01-27 18:02 ` Eli Zaretskii
2020-01-27 18:55 ` VanL
2020-01-27 19:07 ` Eli Zaretskii
2020-02-12 10:32 ` VanL
2020-02-16 2:23 ` VanL
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2a7697zah.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=van@scratch.space \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.