From: Eli Zaretskii <eliz@gnu.org>
To: Kai Ma <justksqsf@gmail.com>
Cc: jb@jeremybryant.net, 71454@debbugs.gnu.org
Subject: bug#71454: 30.0.50; Performance issues with font selection
Date: Mon, 10 Jun 2024 15:59:52 +0300 [thread overview]
Message-ID: <86sexl7y2f.fsf@gnu.org> (raw)
In-Reply-To: <4F59591A-23F6-4DB2-A350-52ED24408F39@gmail.com> (message from Kai Ma on Mon, 10 Jun 2024 14:35:50 +0200)
> From: Kai Ma <justksqsf@gmail.com>
> Date: Mon, 10 Jun 2024 14:35:50 +0200
> Cc: Jeremy Bryant <jb@jeremybryant.net>,
> 71454@debbugs.gnu.org
>
>
>
> > On Jun 10, 2024, at 13:55, Eli Zaretskii <eliz@gnu.org> wrote:
> >
> >> Cc: 71454@debbugs.gnu.org
> >> From: Kai Ma <justksqsf@gmail.com>
> >> Date: Mon, 10 Jun 2024 00:17:55 +0200
> >>
> >>
> >>> On Jun 10, 2024, at 00:10, Jeremy Bryant <jb@jeremybryant.net> wrote:
> >>>
> >>> Would you be able to provide a self-contained series of steps starting
> >>> from emacs -Q?
> >>
> >> On my machine it is extremely easy to reproduce by simply:
> >>
> >> 1. emacs -Q
> >> 2. Switch to *scratch*
> >> 3. Copy the provided text into *scratch*
> >> 4. Emacs will freeze for 17 seconds or so, and it cannot be interrupted by C-g
> >
> > I cannot reproduce this, I get an almost instantaneous redisplay with
> > those characters.
> >
> > When your Emacs eventually displays the text, how many characters are
> > shown as boxes with hex code, and which ones are those?
>
> None are hex code here. They eventually get displayed, but it takes a long time.
Then it definitely sounds like macOS specific. Does anyone know how
Emacs on macOS searches for fonts, and whether there are any
font-caching facilities, either in Emacs or by the OS?
next prev parent reply other threads:[~2024-06-10 12:59 UTC|newest]
Thread overview: 24+ 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 [this message]
2024-06-10 16:42 ` Gerd Möllmann
2024-06-10 17:36 ` Kai Ma
2024-06-10 18:05 ` Gerd Möllmann
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86sexl7y2f.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71454@debbugs.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.