emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Scott Otterson <scotto@sharpleaf.org>
Cc: "Emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: [BUG] after update to 9.5, starting org mode results in cache error messages [9.5 (9.5-gd4e192 @ c:/Users/scott/.emacs.d/straight/build/org/)]
Date: Sun, 31 Oct 2021 11:53:56 +0800	[thread overview]
Message-ID: <87y269n92j.fsf@localhost> (raw)
In-Reply-To: <CAPY3P0T5Wo0BA72Dzzc73DsmkME_fiB=Z3bnvT+qvqjj2s7a0Q@mail.gmail.com>

Scott Otterson <scotto@sharpleaf.org> writes:

> I just updated to org v 9.5, and now, when I open an org file, I get a
> cache error message (between the '=' lines below).  Before 9.5, I didn't
> have this problem.

Thanks for reporting! We are enabling org-element-cache by default.
That's where the warnings are coming from.

> The element is: "(paragraph (:begin 549781 :end 549835 :contents-begin
> ...
>  The real element is: "(paragraph (:begin 549660 :end 549835

This backtrace is really strange. I have seen some advised functions in
your config. Do you happen to advice built-in org-mode functions,
especially from org-element?

Also, if you observe this warning often, can you set
org-element--cache-self-verify to 'backtrace and report the detailed
backtrace next time you see the warning?


  reply	other threads:[~2021-10-31  3:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-31  3:19 [BUG] after update to 9.5, starting org mode results in cache error messages [9.5 (9.5-gd4e192 @ c:/Users/scott/.emacs.d/straight/build/org/)] Scott Otterson
2021-10-31  3:53 ` Ihor Radchenko [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-10-31 19:26 Greg Coladonato
2021-11-01 12:42 ` Ihor Radchenko
2021-11-02  3:25   ` Greg Coladonato
2021-11-02  4:05     ` Ihor Radchenko
2021-11-02  4:33       ` Greg Coladonato
2021-11-02  5:26         ` Ihor Radchenko
2021-11-02 23:06           ` Greg Coladonato
2021-11-03 11:50             ` 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:

  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=87y269n92j.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=scotto@sharpleaf.org \


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