From: Dmitry Alexandrov <dag@gnui.org>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: Is font fallback slow over X11/ssh?
Date: Sun, 31 May 2020 11:16:48 +0300 [thread overview]
Message-ID: <h7vw4iz3.dag@gnui.org> (raw)
In-Reply-To: <CAP_d_8XSyQoPkSSrN5JD1fD=dwto-hv3EMBfe+Rz1HhUm0=BEw@mail.gmail.com> (Yuri Khan's message of "Thu, 28 May 2020 19:11:12 +0700")
[-- Attachment #1: Type: text/plain, Size: 219 bytes --]
> Is font fallback slow over X11/ssh?
FWIW, yes, it is. And thatʼs one of my reasons to prefer server-side font rendering for remote Emacs sessions. I. e. something like:
$ emacs --xrm='Emacs.fontBackend: x'
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-05-31 8:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 12:11 Is font fallback slow over X11/ssh? Yuri Khan
2020-05-31 8:16 ` Dmitry Alexandrov [this message]
2020-05-31 13:13 ` Stefan Monnier
2020-06-04 17:24 ` Dmitry Alexandrov
2020-06-04 21:01 ` Stefan Monnier
2020-06-05 10:32 ` Dmitry Alexandrov
2020-06-05 15:22 ` Stefan Monnier
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=h7vw4iz3.dag@gnui.org \
--to=dag@gnui.org \
--cc=help-gnu-emacs@gnu.org \
--cc=yuri.v.khan@gmail.com \
/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).