From: Ihor Radchenko <yantar92@posteo.net>
To: Keith Waclena <keith@lib.uchicago.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Warning (org-element-cache): org-element--cache: Org parser error [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.3/lisp/org/)]
Date: Mon, 15 Apr 2024 13:48:09 +0000 [thread overview]
Message-ID: <87le5e68km.fsf@localhost> (raw)
In-Reply-To: <x7pluzirfm.fsf@lib.uchicago.edu>
Keith Waclena <keith@lib.uchicago.edu> writes:
> Since upgrading from Emacs v28 to v29 I get this error the first time I
> pull up the agenda via M-x org-agenda:
>
> ⛔ Warning (org-element-cache): org-element--cache: Org parser error in emacs.org::#<marker at 29187 in emacs.org>. Resetting.
> The error was: (error "Invalid search bound (wrong side of point)")
> Backtrace:
> nil
> Please report this to Org mode mailing list (M-x org-submit-bug-report).
>
> The same error is repeated 15 times for 15 different agenda files (with
> different marker values), once per file; most of these markers are at
> end-of-file but not all of them.
>
> When the warning pop up emacs is spinning the CPU and is hung; at that
> moment this command in the shell also hangs:
>
> $ emacsclient --eval '(top-level)'
>
> Emacs tells me to hit C-g 4 times to interrupt, and that works.
>
> After I interrupt it, my agenda works fine until I restart Emacs and
> then it happens again.
>
> Any ideas / hints? Thanks!
Thanks for reporting!
May you try to upgrade to the development version of Org mode?
--
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-04-15 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 19:29 [BUG] Warning (org-element-cache): org-element--cache: Org parser error [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.3/lisp/org/)] Keith Waclena
2024-04-15 13:48 ` Ihor Radchenko [this message]
2024-05-15 11:16 ` 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=87le5e68km.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=keith@lib.uchicago.edu \
/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).