unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
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 16:59:15 +0100	[thread overview]
Message-ID: <m25zgw99gs.fsf@gmail.com> (raw)
In-Reply-To: <m2sgk0j4qj.fsf@scratch.space> (VanL's message of "Tue, 28 Jan 2020 02:31:16 +1100")

>>>>> On Tue, 28 Jan 2020 02:31:16 +1100, VanL <van@scratch.space> said:

    VanL> Robert Pluim <rpluim@gmail.com> writes:
    >> OK, but that has nothing to do with FontBackend. If the default font
    >> is not to your liking, you can change it easily enough.

    VanL> From what I can tell, the Cairo and Harbuzz parts in the Emacs has
    VanL> something to do with FontBackend.   They are preferred to xft, maybe.

Your build will either use Cairo, or XFT. You canʼt have both in the
same build at the same time, and messing with FontBackend is just
going to cause you problems later. And yes, Cairo is preferred,
because libXft is unmaintained, which gives rise to all sorts of
display problems with certain fonts.

    >> The delay I think is inevitable when Emacs has to search through lots
    >> of fonts.

    VanL> OK, but where are those loops in the source code?   And can the initial
    VanL> start phase preload the fonts in memory?   The fonts reside at the X
    VanL> server and client ends.   Why the busy network transfer? 

Preload which fonts? Emacs doesnʼt know which fonts itʼs going to need
until it sees what characters itʼs being asked to display.

Robert



  reply	other threads:[~2020-01-27 15:59 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 [this message]
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=m25zgw99gs.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.
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).