i got the error upon scroll-up-command. [i am not sure if i was in the buffer being reported on for sure, but i always have only one window, so if so, it woudl be oerhaps strange that it would try to font lock something not visible. one thing that would help is if th4e warnings buffer could contain timestamps, so i can know whether the previous warning was just recent or not.]
i set teh variables and tried to repro and was not able to. here is the entire warnings buffer, for recent. i think there are 2 warnings in it. ⛔ Warning (org-element): org-element--cache: Org parser error in prompt-blob.org::52956. Resetting. The error was: (error "Invalid search bound (wrong side of point)") Backtrace: " backtrace-to-string(nil) org-element-at-point() org-adaptive-fill-function() fill-match-adaptive-prefix() fill-context-prefix(52956 52985) visual-wrap-fill-context-prefix(52956 52985) visual-wrap-prefix-function(52956 52986) #f(compiled-function (fun) #<bytecode 0x1bae598aa1fd64bf>)(visual-wrap-prefix-function) jit-lock--run-functions(52956 52986) jit-lock-fontify-now(52956 53766) jit-lock-function(52956) redisplay_internal\\ \\(C\\ function\\)() " Please report this to Org mode mailing list (M-x org-submit-bug-report). ⛔ Warning (org-element): org-element--cache: Org parser error in executive--a.org::150096. Resetting. The error was: (wrong-type-argument integer-or-marker-p nil) Backtrace: " backtrace-to-string(nil) org-element-at-point() org-adaptive-fill-function() fill-match-adaptive-prefix() fill-context-prefix(150096 150155) visual-wrap-fill-context-prefix(150096 150155) visual-wrap-prefix-function(150096 151596) #f(compiled-function (fun) #<bytecode 0x1bad670a092df4bf>)(visual-wrap-prefix-function) jit-lock--run-functions(150096 151596) jit-lock-fontify-now(150096 151596) jit-lock-function(150096) redisplay_internal\\ \\(C\\ function\\)() " Please report this to Org mode mailing list (M-x org-submit-bug-report). On Sun, Jul 20, 2025 at 4:15 PM Samuel Wales <samolog...@gmail.com> wrote: > > i will try, but i doubt that i wil be able to retrigger immediately > aft4r the first trigger. > > On Sun, Jul 20, 2025 at 8:04 AM Ihor Radchenko <yanta...@posteo.net> wrote: > > > > Samuel Wales <samolog...@gmail.com> writes: > > > > > ⛔ Warning (org-element): org-element--cache: Org parser error in > > > fix.org::22506. Resetting. > > > The error was: (wrong-type-argument integer-or-marker-p nil) > > > Backtrace: > > > " backtrace-to-string(nil) > > > org-element-at-point() > > > org-adaptive-fill-function() > > > fill-match-adaptive-prefix() > > > fill-context-prefix(22506 22558) > > > visual-wrap-fill-context-prefix(22506 22558) > > > visual-wrap-prefix-function(22557 22558) > > > #f(compiled-function (fun) #<bytecode > > > 0x1baff79c90b670bf>)(visual-wrap-prefix-function) > > > jit-lock--run-functions(22557 22558) > > > jit-lock-fontify-now(22557 24057) > > > jit-lock-function(22557) > > > redisplay_internal\\ \\(C\\ function\\)() > > > " > > > Please report this to Org mode mailing list (M-x org-submit-bug-report). > > > > When this happens, could you evaluate > > (setq backtrace-on-redisplay-error t) > > (setq debug-on-error t) > > and try to trigger again? > > This should give more meaningful backtrace in *Redisplay-trace* buffer. > > > > -- > > Ihor Radchenko // yantar92, > > Org mode maintainer, > > 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> > > > > -- > The Kafka Pandemic > > A blog about science, health, human rights, and misopathy: > https://thekafkapandemic.blogspot.com -- The Kafka Pandemic A blog about science, health, human rights, and misopathy: https://thekafkapandemic.blogspot.com
