Re: [BUG] org-element--cache: Org parser error [9.6 (release_9.6-90-gf49ee9 @ /home/stefan/.emacs.d/contrib/org-mode/lisp/)]

[Ihor Radchenko]

Stefan  writes:

> (plain-list (:type unordered :begin 712169 :end 712176 :contents-begin 712169 
> :contents-end 712175 :structure ((712169 0 "- " nil "[ ]" nil 712175)) ...))

Curious. What about (org-element-at-point 712029)? (like in your backtrace)

If no error is thrown in this way as well, try to set debug-on-error to
t and trigger the backtrace again. It should be slightly more
informative then.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [BUG] org-element--cache: Org parser error [9.6 (release_9.6-90-gf49ee9 @ /home/stefan/.emacs.d/contrib/org-mode/lisp/)]

[Stefan]

(plain-list (:type unordered :begin 712169 :end 712176 :contents-begin 712169 
:contents-end 712175 :structure ((712169 0 "- " nil "[ ]" nil 712175)) ...))

For the record, the last heading in Stefan.org looks like this:

-- quote --

** DONE [#A] Set alarm clock for presentation
CLOSED: [2022-12-11 Sun 13:38] SCHEDULED: <2022-12-09 Fri 19:00>
:PROPERTIES:
:CREATED:  [2022-12-07 Wed 18:01]
:ID:   efe672fa-9607-4cd2-858e-0ca89838bd56
:END:
:LOGBOOK:
- Refiled on [2022-12-07 Wed 18:01]
:END:

- [ ]


-- endquote--

That's a heading created based on a capture template, where I did not set that 
checklist item.

Best,
 Stefan

On Wed, Dec 14, 2022, at 19:32, Ihor Radchenko wrote:
> Thanks!
>
> What happens if you run M-: (org-element-at-point (point-max))
> from Stefan.org?

Re: [BUG] org-element--cache: Org parser error [9.6 (release_9.6-90-gf49ee9 @ /home/stefan/.emacs.d/contrib/org-mode/lisp/)]

[Ihor Radchenko]

Stefan  writes:

> thanks for the fast reaction.
>
> Here is the backtrace, again from the =a= agenda:
>
> https://gist.githubusercontent.com/stefan2904/0bb5d9db84664a4f4225cd809c294964/raw/e0ac2ec53d4b1d2fed57e440b8fb23157ecbab3d/redacted-backtrace.log

Thanks!

What happens if you run M-: (org-element-at-point (point-max))
from Stefan.org?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [BUG] org-element--cache: Org parser error [9.6 (release_9.6-90-gf49ee9 @ /home/stefan/.emacs.d/contrib/org-mode/lisp/)]

[Stefan]

Hi Ihor, all,

thanks for the fast reaction.

Here is the backtrace, again from the =a= agenda:

https://gist.githubusercontent.com/stefan2904/0bb5d9db84664a4f4225cd809c294964/raw/e0ac2ec53d4b1d2fed57e440b8fb23157ecbab3d/redacted-backtrace.log

Best,
 Stefan

On Wed, Dec 14, 2022, at 16:17, Ihor Radchenko wrote:
> Thanks for reporting!
>
> Could you please set org-element--cache-self-verify to 'backtrace and
> org-element--cache-self-verify-frequency to 1.0? Then, try to reproduce
> the error and post the full (huge) backtrace.
>
> Note that the backtrace will contain parts of your file, so you may
> consider stripping the sensitive parts of sharing it privately.

Re: [BUG] org-element--cache: Org parser error [9.6 (release_9.6-90-gf49ee9 @ /home/stefan/.emacs.d/contrib/org-mode/lisp/)]

[Ihor Radchenko]

Stefan  writes:

> I recently upgraded to Org 9.6 via Git (and to Emacs 28 with nativecomp), and 
> since then I get this kind of warnings all the time. They appear at different 
> spots in my org files and there is nothing special with the headings in 
> question.
>
> This specific warning appears when I load the standard =a= agenda:
>
> ---quote---
>
> Warning (org-element-cache): org-element--cache: Org parser error in 
> Stefan.org::#. Resetting.
>  The error was: (error "Invalid search bound (wrong side of point)")
>  Backtrace:
> "  backtrace-to-string(nil)
>   org-element-at-point(#)
>   org-element-cache-map(#f(compiled-function (el) # -0xe265922b01e7370>) :next-re \"]+)>\" :fail-re 
> \"]+)>\" :narrow t)
>   org-agenda-get-deadlines()

Thanks for reporting!

Could you please set org-element--cache-self-verify to 'backtrace and
org-element--cache-self-verify-frequency to 1.0? Then, try to reproduce
the error and post the full (huge) backtrace.

Note that the backtrace will contain parts of your file, so you may
consider stripping the sensitive parts of sharing it privately.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

[BUG] org-element--cache: Org parser error [9.6 (release_9.6-90-gf49ee9 @ /home/stefan/.emacs.d/contrib/org-mode/lisp/)]

[Stefan]

Hello everyone,

I recently upgraded to Org 9.6 via Git (and to Emacs 28 with nativecomp), and 
since then I get this kind of warnings all the time. They appear at different 
spots in my org files and there is nothing special with the headings in 
question.

This specific warning appears when I load the standard =a= agenda:

---quote---

Warning (org-element-cache): org-element--cache: Org parser error in 
Stefan.org::#. Resetting.
 The error was: (error "Invalid search bound (wrong side of point)")
 Backtrace:
"  backtrace-to-string(nil)
  org-element-at-point(#)
  org-element-cache-map(#f(compiled-function (el) #) :next-re \"]+)>\" :fail-re 
\"]+)>\" :narrow t)
  org-agenda-get-deadlines()
  org-agenda-get-day-entries(\"/home/stefan/PRIVATE/journal/org/Stefan.org\" 
(12 12 2022) :deadline :scheduled :timestamp :sexp)
  apply(org-agenda-get-day-entries 
\"/home/stefan/PRIVATE/journal/org/Stefan.org\" (12 12 2022) (:deadline 
:scheduled :timestamp :sexp))
  org-agenda-list(nil)
  funcall-interactively(org-agenda-list nil)
  call-interactively(org-agenda-list)
  org-agenda(nil)
  funcall-interactively(org-agenda nil)
  call-interactively(org-agenda nil nil)
  command-execute(org-agenda)
"

---endquote---

Emacs  : GNU Emacs 28.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.33, 
cairo version 1.16.0)
 of 2022-05-31
Package: Org mode version 9.6 (release_9.6-90-gf49ee9 @ 
/home/stefan/.emacs.d/contrib/org-mode/lisp/)


Best,
 Stefan