From: Ihor Radchenko <email@example.com>
To: David Conner <firstname.lastname@example.org>
Subject: Re: [BUG] (Doom) Consistently seeing "org-element--cache" problems [9.6 (9.6-??-0c9b30e @ /home/dc/.emacs.doom/.local/straight/build-28.0.90/org/)]
Date: Sat, 29 Jan 2022 23:45:50 +0800 [thread overview]
Message-ID: <877daiwno1.fsf@localhost> (raw)
David Conner <email@example.com> writes:
> Subject: [BUG] (Doom) Consistently seeing "org-element--cache" problems [9.6
> (9.6-??-0c9b30e @
Thanks for the report!
> I was shuffling around the headlines in a newly created org file. The
> error message showed up when I demoted the last headlines under the
> "Notes" headline.
> Here is the org content:
I am unable to reproduce any kind of cache problem using your file on
Note that you are running 2 month old Org mode. Could you try to update
to latest main and check again? If you keep seeing "org-element--cache"
warning messages, please also report the warning text.
> I have also had issues with detangling recently, where it reports that
> it is "not in a babel block", but is searching between completely
> arbitrary characters for the current block. In my literate .doom.d
> config.el & config.org, this always occurs at the same block. I'm unsure
> whether this is related.
I might be related to corrupted cache. If you keep seeing this after the
update, please also try to run M-x org-element-cache-reset and let us
know if it fixes the detangle problem.
next prev parent reply other threads:[~2022-01-29 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 4:07 David Conner
2022-01-29 15:45 ` Ihor Radchenko [this message]
2022-02-02 16:12 ` David Conner
2022-02-03 12:24 ` Ihor Radchenko
2022-04-17 2:36 ` David Conner
2022-04-17 2:49 ` Ihor Radchenko
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).