Morgan Willcock writes:
>> org-element.el has been changed significantly on main compared to bugfix
>> branch.
>
> I remained on the release version but the problem has not reappeared.
>
> Given that the development version has significant changes, and I am not
> able to get a handle on what
Ihor Radchenko writes:
> Morgan Willcock writes:
>
>>> Would you be able to upgrade to the development version of Org mode and
>>> test if the warning disappear?
>>
>> I would be willing to for diagnostic purposes (presumably I would just
>> make sure the development version is earlier in the
Morgan Willcock writes:
>> Would you be able to upgrade to the development version of Org mode and
>> test if the warning disappear?
>
> I would be willing to for diagnostic purposes (presumably I would just
> make sure the development version is earlier in the load-path?) but it
> would be
Ihor Radchenko writes:
> Morgan Willcock writes:
>
>> I've managed to trigger this a couple of times over the last few days,
>> both times the backtrace began by calling flyspell functions. I'm not
>> sure how to re-create the problem, but I thought it best to report it
>> just in case anyone
Morgan Willcock writes:
> I've managed to trigger this a couple of times over the last few days,
> both times the backtrace began by calling flyspell functions. I'm not
> sure how to re-create the problem, but I thought it best to report it
> just in case anyone else is seeing the same thing.
>
I've managed to trigger this a couple of times over the last few days,
both times the backtrace began by calling flyspell functions. I'm not
sure how to re-create the problem, but I thought it best to report it
just in case anyone else is seeing the same thing.
⛔ Warning (org-element-cache):
