From: Ihor Radchenko <yantar92@posteo.net>
To: William Denton <william@williamdenton.org>
Cc: Bruno Cardoso <cardoso.bc@gmail.com>,
Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Things got very slow: profiler output
Date: Sun, 17 Mar 2024 19:33:04 +0000 [thread overview]
Message-ID: <87h6h4y7pr.fsf@localhost> (raw)
In-Reply-To: <3TXoimktsyU1MDZyJsGVrQjZzYs2tevgGzinAsOg-8vVJ-roputyb45wbjVTLdLF1YoTiwptiommSNOYCDMVQNktwzr78qyIonS2m_HAVX4=@williamdenton.org>
William Denton <william@williamdenton.org> writes:
> On Saturday, March 16th, 2024 at 14:56, Ihor Radchenko <yantar92@posteo.net> wrote:
>
>> Did you try setting org-highlight-latex-and-related to nil?
>
> That did it! Thank you! Org is back to normal, fast and responsive. What do you make of all this? Was it just something about my individual setup?
> (In fact I now have it set to '(script entities). Both 'latex and 'native gave me the problems, but this works.)
That's because `org-latex-regexps' is a bit too complex for Emacs regexp
engine in some cases. For some unfortunate Org files, these regexps may
trigger stack overflow while matching.
Eventually, we will switch to parser-based fontification, and the
problem will be solved.
For now, I have no clue how to simplify the problematic regexps without
risking regressions.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-03-17 19:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 5:13 Things got very slow: profiler output William Denton
2024-02-29 9:21 ` Bruno Barbier
2024-02-29 9:28 ` Ihor Radchenko
[not found] ` <notmuch-sha1-998a6a574db756b51dbdd759ff59b5174d99c7f1>
2024-02-29 9:25 ` Bruno Barbier
2024-03-07 16:12 ` William Denton
2024-03-07 17:42 ` Bruno Barbier
2024-03-09 19:27 ` William Denton
2024-03-12 12:43 ` Ihor Radchenko
2024-03-13 23:19 ` Bruno Cardoso
2024-03-14 1:17 ` William Denton
2024-03-14 7:34 ` Gerard Vermeulen
2024-03-14 10:27 ` Bruno Cardoso
2024-03-14 10:22 ` Bruno Cardoso
2024-03-14 21:23 ` Ihor Radchenko
2024-03-15 1:09 ` Bruno Cardoso
2024-03-15 14:24 ` Ihor Radchenko
2024-03-15 16:33 ` Bruno Cardoso
2024-03-15 17:18 ` Ihor Radchenko
2024-03-15 17:49 ` Bruno Cardoso
2024-03-16 8:56 ` Ihor Radchenko
2024-03-16 13:31 ` Bruno Cardoso
2024-03-16 15:56 ` Ihor Radchenko
2024-03-16 18:39 ` William Denton
2024-03-16 18:56 ` Ihor Radchenko
2024-03-17 18:59 ` William Denton
2024-03-17 19:33 ` Ihor Radchenko [this message]
2024-03-16 20:21 ` Bruno Cardoso
2024-03-16 21:14 ` Ihor Radchenko
2024-03-17 13:02 ` Bruno Cardoso
2024-03-17 14:19 ` Ihor Radchenko
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6h4y7pr.fsf@localhost \
--to=yantar92@posteo.net \
--cc=cardoso.bc@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=william@williamdenton.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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).