From: Evan Moses <emoses@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 42522@debbugs.gnu.org
Subject: bug#42522: Emacs 27: 100% CPU when setting mode-name with ligatures
Date: Sat, 25 Jul 2020 14:13:17 -0700 [thread overview]
Message-ID: <DE74D723-5C21-42C8-9972-7822667AB6B6@gmail.com> (raw)
In-Reply-To: <834kpwdscw.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]
FYI I was following the instructions here: https://github.com/tonsky/FiraCode/wiki/Emacs-instructions#using-composition-char-table to get Fira Code ligatures globally. It so happens that C-modes will add “//“ to the mode name in certain configurations; I just pared this down to a minimal repro case.
--
Evan Moses
emoses@gmail.com
> On Jul 24, 2020, at 11:25 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>
>
>>
>> From: Evan Moses <emoses@gmail.com>
>> Date: Fri, 24 Jul 2020 14:35:50 -0700
>>
>> To reproduce, evaluate this
>>
>> (set-char-table-range composition-function-table 47 '([".\\(?:\\(?:\\*\\*\\|//\\|==\\)\\|[*/=>]\\)" 0
>> font-shape-gstring]))
>>
>> And then evaluate
>>
>> (setq mode-name "test//")
>>
>> Emacs will become unresponsive and consume 100% CPU.
>
> It doesn't hang here. Could this be macOS-specific? Or maybe the
> problem happens only with some fonts? Does it happen in "emacs -Q"?
>
> In any case, did you really mean for Emacs to produce ligatures on the
> mode line? More generally, what kind of ligatures are you trying to
> produce with this setup?
[-- Attachment #2: Type: text/html, Size: 2330 bytes --]
prev parent reply other threads:[~2020-07-25 21:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 21:35 bug#42522: Emacs 27: 100% CPU when setting mode-name with ligatures Evan Moses
2020-07-25 6:24 ` Eli Zaretskii
2020-07-25 17:22 ` Robert Pluim
2020-07-25 17:27 ` Eli Zaretskii
2020-08-13 0:18 ` Stefan Kangas
2020-08-13 16:18 ` Evan Moses
2020-08-13 16:54 ` Stefan Kangas
2020-07-25 21:13 ` Evan Moses [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DE74D723-5C21-42C8-9972-7822667AB6B6@gmail.com \
--to=emoses@gmail.com \
--cc=42522@debbugs.gnu.org \
--cc=eliz@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.
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.