unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Vladimir Nikishkin <lockywolf@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: A certain unicode character makes -git Emacs eat all the CPU and become very slow.
Date: Sun, 8 May 2022 16:26:39 +0800	[thread overview]
Message-ID: <CA+A2iZYtiiQjNjJwhoZukcDGz916_kBtBxp7cdqjCdVVoMkzZQ@mail.gmail.com> (raw)
In-Reply-To: <87r1589ry8.fsf@yahoo.com>

Okay, I have had some progress.

The font that causes Emacs to misbehave is AdobeBlank, often shipped
in the "Google Fonts" (not Google Noto) package.

It does not have to be used for display, it is its presence that makes
Emacs cog a core.

That "Blank" font covers all of Unicode, but every glyph is an empty
picture. I guess it is designed for the situations when there may be
symbols from out of the installed range, but when displaying "tofu" is
not desired, say, on public displays.

But in any case, it is a fairly standard, widespread font. I don't
think Emacs should behave like this in its presence.

On Thu, 5 May 2022 at 18:47, Po Lu <luangruo@yahoo.com> wrote:
>
> Vladimir Nikishkin <lockywolf@gmail.com> writes:
>
> > I have rebuilt Emacs without pgtk, and to the same effect. :(
>
> Too bad, I can't see anything wrong in the font log either.  I'm at a
> loss.  Try uninstalling fonts from your system one-by-one, and see when
> the problem goes away.
>
> Thanks.



-- 
Yours sincerely, Vladimir Nikishkin
(Sent from GMail web interface.)



  reply	other threads:[~2022-05-08  8:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05  4:03 A certain unicode character makes -git Emacs eat all the CPU and become very slow Vladimir Nikishkin
2022-05-05  5:04 ` Po Lu
2022-05-05  5:43   ` Vladimir Nikishkin
2022-05-05 10:00     ` Vladimir Nikishkin
2022-05-05 10:47       ` Po Lu
2022-05-08  8:26         ` Vladimir Nikishkin [this message]
2022-05-08  8:55           ` Po Lu
2022-05-08  8:55           ` Eli Zaretskii
2022-05-05  6:11 ` 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=CA+A2iZYtiiQjNjJwhoZukcDGz916_kBtBxp7cdqjCdVVoMkzZQ@mail.gmail.com \
    --to=lockywolf@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=luangruo@yahoo.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.
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).