Julien Palard <[email protected]> writes: > Got a very strange error today, hopefully captured with (setq > debug-on-error t). > > Very strange because: > ... > So maybe there's a cache somewhere that I'm not aware of, that was > invalidated during my tests?
Yeah, most likely parser cache. > Anyway, here's the debugger output, maybe someone can understand > something out of it, but as I'm no longer able to reproduce it, it's > probably of low value: > > Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil) > org-element-item-parser(962363 ((961733 0 "- " nil nil nil 961796) (961796 > 0 "- " nil nil nil 961859) (961859 0 "- " nil nil nil 961922) (961922 0 "- " > nil nil nil 961985) (961985 0 "- " nil nil nil 962048) (962048 0 "- " nil nil > nil 962111) (962111 0 "- " nil nil nil 962174) (962174 0 "- " nil nil nil > 962237) (962237 0 "- " nil nil nil 962300) (962300 0 "- " nil nil nil > 962363)) t) No insights, unfortunately. I suspect that it might be something about 962363 point not being at the beginning of the list, but no clue what could have caused it. If you experience errors like this one regularly, setting org-element--cache-self-verify to 'backtrace can reveal more clues. -- 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>
