From: VanL <van@scratch.space>
To: help-gnu-emacs@gnu.org
Subject: Re: 26.3, 28; Set Default Font... CMU Typewriter Text
Date: Tue, 28 Jan 2020 00:08:35 +1100 [thread overview]
Message-ID: <m2o8up3v3g.fsf@scratch.space> (raw)
In-Reply-To: m2wo9e7znk.fsf@gmail.com
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
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.
The creepy crawly spidery font that occurs in Emacs-28 between quote
marks, by default, was something I lived with to the moment it was
raised in a thread on emacs-devel. Then on, I followed the discussion
on fonts to improve that setting. And, pieced together the info that
is at the head of this thread. Another discomfort I live with is a
long delay when I first open a file with a mix of CJ asia east fonts.
The delay is about as long as the time it takes to transfer a 4Gb data
file. Attached is a capture of the packet traffic activity.
[-- Attachment #2: delay-like-waiting-for-duration-of-4Gb-transfer --]
[-- Type: image/png, Size: 10082 bytes --]
[-- Attachment #3: Type: text/plain, Size: 190 bytes --]
That delay occurred due to the fonts included below from the signature file.
-- VL
李 A fallen flower
德 Returning to
煒 The branch? its a butterfly (蝴蝶). -Bashō (芭蕉)
next prev parent reply other threads:[~2020-01-27 13:08 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 [this message]
2020-01-27 14:24 ` Robert Pluim
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
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=m2o8up3v3g.fsf@scratch.space \
--to=van@scratch.space \
--cc=help-gnu-emacs@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.
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).