Ihor Radchenko writes:
> Thanks! It looks like you found the culprit.
>
> `org-startup-align-all-tables' triggers a function that changes buffer
> contents (tables) during Org loading. For same reason, this function is
> executed with modification hooks being suppressed and cache missing the
>
Bastien, I need your comment on the old commit of yours.
Stefan writes:
>> 2. If you can, try to load Emacs with minimal Org-related settings.
>>Then, try to load agenda and let me know if you see the warning.
>
> I did some manual bisecting of my config, and I noticed that the warnings in
Hi,
On Thu, Dec 15, 2022, at 13:16, Ihor Radchenko wrote:
> 1. Check the value of `org-element--cache-change-tic' right after
>opening an Org file
first its 1,
(when I start fresh and add 1 byte to the buffer the value is 13955)
> and the values of `after-change-functions' and
>
Stefan writes:
> sorry, I was not aware of that. I am sending the full backtrace unredacted to
> you directly.
>
> The respective org files are in a git repo, and there I don't see any edits
> in the files since starting emacs (also not after manually saving all org
> buffers).
>
> Let me
Hello,
sorry, I was not aware of that. I am sending the full backtrace unredacted to
you directly.
The respective org files are in a git repo, and there I don't see any edits in
the files since starting emacs (also not after manually saving all org buffers).
Let me know if you need anything
Stefan writes:
> While trying to reproduce the "Org parser error" error issue (see other
> thread), I got multiple "Cached element is incorrect" warnings (backtrace
> excerpt below).
>
> Here is one that appeared when trying to loading the =t= agenda:
Thanks, but a small portion of the
While trying to reproduce the "Org parser error" error issue (see other
thread), I got multiple "Cached element is incorrect" warnings (backtrace
excerpt below).
Here is one that appeared when trying to loading the =t= agenda:
-- quote --
Warning (org-element-cache): org-element--cache:
