From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Kai Ma <justksqsf@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
71454@debbugs.gnu.org, Jeremy Bryant <jb@jeremybryant.net>
Subject: bug#71454: 30.0.50; Performance issues with font selection
Date: Mon, 10 Jun 2024 20:05:41 +0200 [thread overview]
Message-ID: <m2le3cd66i.fsf@pro2.fritz.box> (raw)
In-Reply-To: <3124ED1B-6E42-48D9-B899-520AD54DCD0C@gmail.com> (Kai Ma's message of "Mon, 10 Jun 2024 19:36:24 +0200")
Kai Ma <justksqsf@gmail.com> writes:
>> On Jun 10, 2024, at 18:42, Gerd Möllmann <gerd.moellmann@gmail.com> wrote:
>> […]
>> Maybe use the Font Book app and see if the fonts are all valid? (Start
>> Font Book, choose All Fonts, select them all with Command + A, then
>> context menu on the selectoin and choose Validate.)
>
> I do get some warnings. Font Book shows “52 minor problems were
> found”. Most are “Duplicate fonts”, but there are also real warnings
> like “name table structure”.
>
> To clear these warnings, I moved all font files in ~/Library/Fonts
> elsewhere, but the problem still persists, though the delay for the
> testing text is much shorter (about 5s now).
Progress :-).
Rumours have it that one can clear system caches (just to make sure) by
performing a safe boot (https://support.apple.com/en-gb/116946), and
then restarting normally.
And then there is the atsutil command line utitlity. Though I must say
that I never had to use that one, and so I can't say if it's
dangerous... (man atsutil).
next prev parent reply other threads:[~2024-06-10 18:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-09 18:56 bug#71454: 30.0.50; Performance issues with font selection Kai Ma
2024-06-09 22:10 ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-09 22:17 ` Kai Ma
2024-06-09 22:34 ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-10 2:14 ` Kai Ma
2024-06-10 12:04 ` Eli Zaretskii
2024-06-09 23:10 ` Jim Porter
2024-06-10 2:18 ` Kai Ma
2024-06-10 11:53 ` Eli Zaretskii
2024-06-10 16:31 ` Jim Porter
2024-06-10 17:35 ` Eli Zaretskii
2024-06-10 11:55 ` Eli Zaretskii
2024-06-10 12:35 ` Kai Ma
2024-06-10 12:59 ` Eli Zaretskii
2024-06-10 16:42 ` Gerd Möllmann
2024-06-10 17:36 ` Kai Ma
2024-06-10 18:05 ` Gerd Möllmann [this message]
2024-06-10 11:58 ` Eli Zaretskii
2024-06-10 12:34 ` Kai Ma
2024-06-10 13:03 ` Eli Zaretskii
[not found] ` <22612F93-FC37-48E8-8137-E9FF6F5B3A0D@gmail.com>
2024-09-27 6:32 ` Eli Zaretskii
2024-09-27 7:51 ` Kai Ma
2024-09-27 10:29 ` Eli Zaretskii
2024-09-28 3:36 ` Gerd Möllmann
2024-10-12 11:20 ` Eli Zaretskii
2024-10-15 20:34 ` Kai Ma
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=m2le3cd66i.fsf@pro2.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=71454@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jb@jeremybryant.net \
--cc=justksqsf@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.
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).