emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Colin Baxter 😺" <m43cap@yandex.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: , emacs-orgmode@gnu.org
Subject: Re: org-element-cache warning even when off
Date: Thu, 02 Dec 2021 11:13:05 +0000	[thread overview]
Message-ID: <87wnknnttq.fsf@yandex.com> (raw)
In-Reply-To: <87h7br71cc.fsf@localhost> (Ihor Radchenko's message of "Thu, 02 Dec 2021 18:22:43 +0800")

>>>>> Ihor Radchenko <yantar92@gmail.com> writes:

    > Colin Baxter 😺 <m43cap@yandex.com> writes:
    >> I do not have an org-persist cache present. So I wonder where is
    >> the cache that I am supposedly corrupting.

    > That warning is shown when org-element--parse-to throws an error
    > (the parser fails). Apparently, there is some problem with Org
    > parser.

    >> Warning (org-element-cache): org-element--cache: Cache corruption
    >> detected in todo.habits.org::539. Resetting.

    > Can you try to copy the file text around 539 buffer point into
    > separate Org file and check if you are seeing this kind of error
    > there?

I have done this but now do not see any warning. Further, I now don't
seem to be able to re-produce the issue at all. It could that the
original warning was spurious and reflected some stale state. I did have
multiple emacsen open at the time.

I normally have org-persist on, but occasionally I need to do multiple
edits on an agenda file. On those occasions, I switch org-persist off
and move its cache out of the way in order to avoid cache corruption
warnings and to keep the syntax highlighting. I will look out for any
cache warnings if I edit any agenda files by hand again.


Best wishes,

Colin Baxter.


  reply	other threads:[~2021-12-02 11:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-02 10:03 org-element-cache warning even when off Colin Baxter 😺
2021-12-02 10:22 ` Ihor Radchenko
2021-12-02 11:13   ` Colin Baxter 😺 [this message]
2021-12-02 11:22     ` 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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wnknnttq.fsf@yandex.com \
    --to=m43cap@yandex.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).