From: Morgan Willcock <morgan@ice9.digital>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Flyspell triggers "Warning (org-element-cache): org-element--cache" [9.6.18 ( @ /home/mwillcock/.emacs.d/elpa/org-9.6.18/)]
Date: Sat, 09 Mar 2024 13:35:06 +0000 [thread overview]
Message-ID: <87edcjjzp1.fsf@ice9.digital> (raw)
In-Reply-To: <87a5o8qud3.fsf@localhost> (Ihor Radchenko's message of "Sat, 10 Feb 2024 14:14:32 +0000")
Ihor Radchenko <yantar92@posteo.net> writes:
> Morgan Willcock <morgan@ice9.digital> 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 tricky to know for sure whether it had made a difference unless
>> I can get a better handle on what triggers it.
>
> You may refer to https://orgmode.org/manual/Installation.html for
> instructions.
>
>> Are there already changes in the development version which you think
>> would be relevant to this problem?
>
> 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 causes the problem (I imagine it is a
general cache problem and not something caused by flyspell), feel free
to close the bug report.
--
Morgan Willcock
next prev parent reply other threads:[~2024-03-09 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 10:33 [BUG] Flyspell triggers "Warning (org-element-cache): org-element--cache" [9.6.18 ( @ /home/mwillcock/.emacs.d/elpa/org-9.6.18/)] Morgan Willcock
2024-02-09 11:39 ` Ihor Radchenko
2024-02-09 20:04 ` Morgan Willcock
2024-02-10 14:14 ` Ihor Radchenko
2024-03-09 13:35 ` Morgan Willcock [this message]
2024-03-12 12:36 ` Ihor Radchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87edcjjzp1.fsf@ice9.digital \
--to=morgan@ice9.digital \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.