From: Moses <moses.mason@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 32159@debbugs.gnu.org
Subject: bug#32159: 26.1; inhibit-compacting-font-caches does not fix all fonts lagging issue
Date: Sun, 15 Jul 2018 05:50:26 +0000 [thread overview]
Message-ID: <CAAYZpmRMJW9bVisJRLja0yEg-rKQ0z3XYfSHanw0ZD7ubVQoFg@mail.gmail.com> (raw)
In-Reply-To: <83muut9q8m.fsf@gnu.org>
You are right. I got 5906 installed fonts returned from (length
(x-list-fonts "*")). However, this still a problem, which is really
annoying when editing files that contain more than one language. Other
editor does not have the similar issue. I am not an expert, but as far
as I know, the font fallback link is already stored in the register
under key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\FontLink\SystemLink, why Emacs still needs to search
fonts multiple times?
On Sun, Jul 15, 2018 at 2:39 AM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Moses <moses.mason@gmail.com>
> > Date: Sun, 15 Jul 2018 00:02:13 +0000
> >
> > For bug#24938, I have to set inhibit-compacting-font-caches to non-nil
> > [0] to fix the lagging issue. It fixes almost but not all the
> > problems. Lagging reappears when I opening a multi languages file
> > (e.g. M-x view-hello-file), Emacs could become very very slow until
> > the file is completely opened.
>
> That lagging might have a valid reason: how many fonts do you have
> installed? What does (length (x-list-fonts "*")) return?
>
> If you have many fonts, Emacs will search them all to find a suitable
> one, and if some characters in HELLO don't have fonts, it will search
> them several times. That might take time. If the lagging disappears
> once you display the entire file, that is most probably the reason.
next prev parent reply other threads:[~2018-07-15 5:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-15 0:02 bug#32159: 26.1; inhibit-compacting-font-caches does not fix all fonts lagging issue Moses
2018-07-15 2:39 ` Eli Zaretskii
2018-07-15 5:50 ` Moses [this message]
2018-07-15 14:41 ` Eli Zaretskii
2018-07-16 2:35 ` Moses
2018-07-16 3:34 ` Eli Zaretskii
2018-07-17 1:38 ` Moses
2018-07-17 2:38 ` Eli Zaretskii
[not found] ` <<83in5ga7dc.fsf@gnu.org>
2018-07-15 16:50 ` Drew Adams
2018-07-15 18:53 ` Eli Zaretskii
2018-07-16 3:43 ` net june
2018-07-16 14:24 ` Eli Zaretskii
[not found] ` <<<83in5ga7dc.fsf@gnu.org>
[not found] ` <<0c4b0a47-267d-4c4d-8d1f-6a562ac7519b@default>
[not found] ` <<837elw9vp9.fsf@gnu.org>
2018-07-15 19:43 ` Drew Adams
2018-07-16 14:22 ` Eli Zaretskii
2018-07-17 2:13 ` Moses
2018-07-17 2:40 ` Eli Zaretskii
2018-07-17 4:22 ` Moses
2018-07-17 15:05 ` Eli Zaretskii
2018-07-19 13:41 ` Eli Zaretskii
2018-07-19 15:56 ` Drew Adams
2018-07-22 5:45 ` Moses
2018-07-22 14:06 ` Eli Zaretskii
2018-07-22 14:52 ` Moses
2018-07-22 15:14 ` Eli Zaretskii
2018-07-22 15:41 ` Moses
2018-07-22 16:02 ` Eli Zaretskii
2018-07-17 10:24 ` Andy Moreton
2018-07-17 15:52 ` Eli Zaretskii
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=CAAYZpmRMJW9bVisJRLja0yEg-rKQ0z3XYfSHanw0ZD7ubVQoFg@mail.gmail.com \
--to=moses.mason@gmail.com \
--cc=32159@debbugs.gnu.org \
--cc=eliz@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).