From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: A certain unicode character makes -git Emacs eat all the CPU and become very slow.
Date: Thu, 05 May 2022 09:11:44 +0300 [thread overview]
Message-ID: <83h76433vj.fsf@gnu.org> (raw)
In-Reply-To: <CA+A2iZaH-KTD=S+2MnS+Nrb=R+jA934AS7is3e+K_NAZOPnhRw@mail.gmail.com> (message from Vladimir Nikishkin on Thu, 5 May 2022 12:03:33 +0800)
> From: Vladimir Nikishkin <lockywolf@gmail.com>
> Date: Thu, 5 May 2022 12:03:33 +0800
>
> Notably, this character: ⮮
> In Unicode this is U+2BAE
I see no such problems here, FWIW. This is with today's master
branch. What you see is most probably related to the fonts you have
installed on that system.
prev parent reply other threads:[~2022-05-05 6:11 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
2022-05-08 8:55 ` Po Lu
2022-05-08 8:55 ` Eli Zaretskii
2022-05-05 6:11 ` Eli Zaretskii [this message]
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=83h76433vj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).