From: VanL <van@scratch.space>
To: help-gnu-emacs@gnu.org
Subject: Re: 26.3, 28; Set Default Font... CMU Typewriter Text
Date: Wed, 12 Feb 2020 21:32:43 +1100 [thread overview]
Message-ID: <m2sgjg6qpg.fsf@scratch.space> (raw)
In-Reply-To: 83h80goh05.fsf@gnu.org
>> (custom-set-faces
>> '(default ((t (:background "gainsboro" :foreground "black" :height
>> 201 :family "CMU Typewriter Text" :foundry "nil" :slant normal
>> :weight light :width normal))))...
>
> With this, I see no reason for you to mess with Emacs.FontBackend in
> .Xdefaults. (However, I suggest to use :font in the customization
> instead of relying on :family.)
That :family keyword in that line is controlled by the M-x customize
interface inserting to the Emacs's initial configuration setup
file... well, anyway, I had hoped to learn something about the UTF-8 and
Unicode by messing with Emacs.FontBackend in .Xdefaults. But it wasn't
the original driving intent. I only wanted to get a better looking font
and not the particularly ugly default in scarey quote in emacs-28 build
2020-01-05.
plan9port/font/sample
from http://www.columbia.edu/kermit/utf8.html
That file sampling various languages displays relatively immediately.
Like under 2.0 seconds. I don't experience the delay like waiting for 4Gb
to transfer before a file with multiple languages displays.
--
OK. I got a good idea. Who is the fastest will win. Boeing. SpaceX. Go...
next prev parent reply other threads:[~2020-02-12 10:32 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
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 [this message]
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=m2sgjg6qpg.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).