Hi Ihor,
Than you for the response! I tried the fix you suggested, but I still
see this:
Warning (org-element-cache): org-element--cache: Org parser error in
2022-log.org::179869. Resetting.
The error was: (error "Invalid search bound (wrong side of point)")
Backtrace:
" backtrace-to-string(nil)
org-element-at-point(179869)
org-element--cache-persist-before-write((elisp org-element--cache)
(:hash \"63193836117540f39113c129b8de99c6\" :file
\"/home/cro/org/log/2022-log.org\" :inode 23336608))
run-hook-with-args-until-success(org-element--cache-persist-before-write
(elisp org-element--cache) (:hash \"63193836117540f39113c129b8de99c6\"
:file \"/home/cro/org/log/2022-log.org\" :inode 23336608))
#f(compiled-function (v) #<bytecode -0x148a5c2ab59ba2da>)((elisp
org-element--cache))
#f(compiled-function (elt) #<bytecode 0x43f3d6737afc546>)((elisp
org-element--cache))
mapc(#f(compiled-function (elt) #<bytecode 0x43f3d6737afc546>)
((elisp org-element--headline-cache) (elisp org-element--cache)))
seq-do(#f(compiled-function (elt) #<bytecode 0x43f3d6737afc546>)
((elisp org-element--headline-cache) (elisp org-element--cache)))
seq-find(#f(compiled-function (v) #<bytecode -0x148a5c2ab59ba2da>)
((elisp org-element--headline-cache) (elisp org-element--cache)))
org-persist-write(((elisp org-element--headline-cache) (elisp
org-element--cache)) (:hash \"63193836117540f39113c129b8de99c6\" :file
\"/home/cro/org/log/2022-log.org\" :inode 23336608) t)
org-persist-write-all(#<buffer 2022-log.org>)
org-persist-write-all-buffer()
kill-buffer(#<buffer 2022-log.org>)
kill-current-buffer()
funcall-interactively(kill-current-buffer)
call-interactively(kill-current-buffer nil nil)
command-execute(kill-current-buffer)
"
Again other than the warning message, nothing seems to be broken, but
it's annoying.
I also see something similar when I close the tab with
centaur-tabs-buffer-close-tab.
~ Cristi
On 6/23/22 07:20, Ihor Radchenko wrote:
Cristi Constantin <cristi.constan...@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
