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: Mon, 16 Jul 2018 10:35:07 +0800 [thread overview]
Message-ID: <CAAYZpmSV1CjXUE9BrKW1GZyx3-MpnzEy-BvUfVtB4zC_PT2cjA@mail.gmail.com> (raw)
In-Reply-To: <83in5ga7dc.fsf@gnu.org>
On Sun, Jul 15, 2018 at 2:41 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Moses <moses.mason@gmail.com>
> > Date: Sun, 15 Jul 2018 05:50:26 +0000
> > Cc: 32159@debbugs.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.
>
> Do some of the characters in HELLO display as boxes with hex code
> inside them, and if so, do you see slow-down when Emacs is about to
> display those characters? If the answer to both question is YES, I
> can suggest a customization to try that might help you avoid the
> slowdown (assuming you don't need to be able to display characters
> from those scripts), but please tell what characters are involved in
> this.
Nope...all characters in the HELLO file can be display correctly
without a problem, the lagging issue only appears while opening the
file. Once it already opened, there is no more slowdown.
> > Other editor does not have the similar issue.
>
> AFAIK, no other editor supports such a large variety of fonts.
I mean other editors do not have slowdown problem while opening such a
relatively small file. They are not as mighty as Emacs of course.
That's why I am using Emacs to process editing :)
> > 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?
>
> I don't think that Registry setting is relevant to the issue at hand.
> Emacs looks for fonts based on its internal database of features
> required by each script.
next prev parent reply other threads:[~2018-07-16 2:35 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
2018-07-15 14:41 ` Eli Zaretskii
2018-07-16 2:35 ` Moses [this message]
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=CAAYZpmSV1CjXUE9BrKW1GZyx3-MpnzEy-BvUfVtB4zC_PT2cjA@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).