From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 53203@debbugs.gnu.org, my.old.email.sucked@gmail.com
Subject: bug#53203: Comment with lots of color codes crashes or hangs emacs in scss-mode
Date: Thu, 13 Jan 2022 10:58:34 +0200 [thread overview]
Message-ID: <8335ls3tc5.fsf@gnu.org> (raw)
In-Reply-To: <87wnj486il.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 13 Jan 2022 08:00:18 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Colin <my.old.email.sucked@gmail.com>, 53203@debbugs.gnu.org
> Date: Thu, 13 Jan 2022 08:00:18 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > It seems to infloop in JIT font-lock, and the culprit seems to be this
> > part of font-lock-keywords:
> >
> > ;; Even though pseudo-elements should be prefixed by ::, a
> > ;; single colon is accepted for backward compatibility.
> > "\\(?:\\(:" (regexp-opt (append css-pseudo-class-ids
> > css-pseudo-element-ids)
> > t)
>
> Trying to understand the regexp used for scss here, I think that bit is
> somewhat innocuous -- it just matches those words.
>
> ;; Even though pseudo-elements should be prefixed by ::, a
> ;; single colon is accepted for backward compatibility.
> "\\(?:\\(:" (regexp-opt (append css-pseudo-class-ids
> css-pseudo-element-ids)
> t)
> "\\|::" (regexp-opt css-pseudo-element-ids t) "\\)"
I posted that because I saw this regexp in the backtrace obtained by
interrupting the infloop.
next prev parent reply other threads:[~2022-01-13 8:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 7:20 bug#53203: Comment with lots of color codes crashes or hangs emacs in scss-mode Colin
2022-01-12 13:16 ` Eli Zaretskii
2022-01-13 7:00 ` Lars Ingebrigtsen
2022-01-13 8:58 ` Eli Zaretskii [this message]
2022-05-14 10:34 ` Simen Heggestøyl
2022-05-14 12:02 ` Lars Ingebrigtsen
2022-05-14 12:38 ` Lars Ingebrigtsen
2022-05-14 13:30 ` Lars Ingebrigtsen
2022-05-14 15:33 ` Lars Ingebrigtsen
2022-05-15 10:45 ` Simen Heggestøyl
2022-05-15 12:14 ` Lars Ingebrigtsen
2022-05-15 14:46 ` Simen Heggestøyl
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=8335ls3tc5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53203@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=my.old.email.sucked@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.