From: Ihor Radchenko <yantar92@posteo.net>
To: William Denton <william@williamdenton.org>
Cc: Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: (jit-lock-function 1) signaled (error "Stack overflow in regexp matcher")
Date: Sun, 18 Feb 2024 16:01:48 +0000 [thread overview]
Message-ID: <87zfvxrcb7.fsf@localhost> (raw)
In-Reply-To: <FZJ8oJRORAT8iFmefpSyweakeVsKLN3r8jG7jzn01Bshp_oIQvugb0NFQRPdxelQNPEn6oFuNL3O4rqEeDDQw-Zc8NNBPXlWoO_1i1761CE=@williamdenton.org>
William Denton <william@williamdenton.org> writes:
> On Thursday, February 15th, 2024 at 15:40, William Denton <william@williamdenton.org> wrote:
>
>> I am having a problem I've never seen before: Org can't handle anything more in a large file I have!
>>
>> This file is where I keep my notes day to day for work, with headings for months and days and categories of work, with a lot of notes and clocking in and out. It has about 10,000 lines and is about 550K in size.
>
> Update: moving the 600-line clock table in that file to another file fixed the problem. (In that new file, it generates its clock table from the clocking in the remote file, the old one.)
It means that Org gives Emacs too complex regexp somewhere.
There is no easy way to fix such issues without having a reproducer and
trying to play around with the problematic regexp.
Emacs regexp engine has some rough edges when regexps get complex.
--
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>
prev parent reply other threads:[~2024-02-18 14:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 20:40 (jit-lock-function 1) signaled (error "Stack overflow in regexp matcher") William Denton
2024-02-15 22:30 ` William Denton
2024-02-18 16:01 ` Ihor Radchenko [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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zfvxrcb7.fsf@localhost \
--to=yantar92@posteo.net \
--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).