emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Ihor Radchenko <yantar92@gmail.com>
To: cristi.constantin@posteo.ie
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] random org-mode warning [9.5.4 (9.5.4-g7c61a3 @ /home/cro/.emacs.default/straight/build/org/)]
Date: Thu, 23 Jun 2022 14:20:39 +0800	[thread overview]
Message-ID: <87fsjv7vew.fsf@localhost> (raw)
In-Reply-To: <d96c24d7-7572-90b6-47d0-47120d942de1@posteo.net>

Cristi Constantin <cristi.constantin@posteo.net> writes:

> I'm just editing my normal org log files and I started seeing the errors 
> above after I upgraded to latest org-mode.
> I think I didn't upgrade for a month, so this bug is pretty new.
> It doesn't seem to do anything weird, but I see this traceback a few 
> times a day.
>
> This is the full error, so I'm reporting as requested:
>
>
> Warning (org-element-cache): org-element--cache: Org parser error in 
> 2022-log.org::178496. Resetting.
> The error was: (error "Invalid search bound (wrong side of point)")
> Backtrace:
> " backtrace-to-string(nil)
> org-element-at-point(178496)
> org-element--cache-persist-before-write((elisp org-element--cache)

Thanks for reporting!

Will it help if you add the following to you config?

(defun org-persist-clear-caches (&rest _)
  "Clear read/write caches for org-persist."
  (clrhash org-persist--write-cache)
  (clrhash org-persist--read-cache)
  nil)
  
(add-hook 'org-persist-before-read-hook #'org-persist-clear-caches)
(add-hook 'org-persist-before-write-hook #'org-persist-clear-caches)

Best,
Ihor

next prev parent reply	other threads:[~2022-06-23  6:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 11:50 [BUG] random org-mode warning [9.5.4 (9.5.4-g7c61a3 @ /home/cro/.emacs.default/straight/build/org/)] Cristi Constantin
2022-06-23  6:20 ` Ihor Radchenko [this message]
2022-06-23 15:16   ` Cristi Constantin
2022-06-27  8:50     ` Ihor Radchenko
2022-06-29  2:10     ` Ihor Radchenko
2022-07-01 11:04       ` Cristi Constantin

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=87fsjv7vew.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=cristi.constantin@posteo.ie \
    --cc=emacs-orgmode@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

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).