From: Kai Ma <justksqsf@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Jeremy Bryant <jb@jeremybryant.net>, 71454@debbugs.gnu.org
Subject: bug#71454: 30.0.50; Performance issues with font selection
Date: Mon, 10 Jun 2024 14:35:50 +0200 [thread overview]
Message-ID: <4F59591A-23F6-4DB2-A350-52ED24408F39@gmail.com> (raw)
In-Reply-To: <865xuh9fmt.fsf@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.
next prev parent reply other threads:[~2024-06-10 12:35 UTC|newest]
Thread overview: 20+ 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 [this message]
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
2024-06-10 11:58 ` Eli Zaretskii
2024-06-10 12:34 ` Kai Ma
2024-06-10 13:03 ` 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=4F59591A-23F6-4DB2-A350-52ED24408F39@gmail.com \
--to=justksqsf@gmail.com \
--cc=71454@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jb@jeremybryant.net \
/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).