From: Ihor Radchenko <yantar92@posteo.net>
To: Stefan <org@stefan.failing.systems>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-element--cache: (org-agenda) Cached element is incorrect [9.6 (release_9.6-90-gf49ee9 @ /home/stefan/.emacs.d/contrib/org-mode/lisp/)]
Date: Thu, 15 Dec 2022 12:16:40 +0000 [thread overview]
Message-ID: <87len8uajb.fsf@localhost> (raw)
In-Reply-To: <52739b43-b836-44db-a250-7323ff8d294c@app.fastmail.com>
Stefan <org@stefan.failing.systems> writes:
> sorry, I was not aware of that. I am sending the full backtrace unredacted to you directly.
>
> The respective org files are in a git repo, and there I don't see any edits in the files since starting emacs (also not after manually saving all org buffers).
>
> Let me know if you need anything else.
Thanks!
This still looks quite strange.
Can you please:
1. Check the value of `org-element--cache-change-tic' right after
opening an Org file and the values of `after-change-functions' and
`after-change-functions' in Org buffer after you see the warning.
2. If you can, try to load Emacs with minimal Org-related settings.
Then, try to load agenda and let me know if you see the warning.
It looks to me like you have something unusual in your Org setup or
some third-party package interfering.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2022-12-15 12:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 21:24 [BUG] org-element--cache: (org-agenda) Cached element is incorrect [9.6 (release_9.6-90-gf49ee9 @ /home/stefan/.emacs.d/contrib/org-mode/lisp/)] Stefan
2022-12-15 8:14 ` Ihor Radchenko
2022-12-15 11:58 ` Stefan
2022-12-15 12:16 ` Ihor Radchenko [this message]
2022-12-15 18:05 ` Stefan
2022-12-15 18:42 ` Ihor Radchenko
2023-01-02 7:29 ` 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=87len8uajb.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=org@stefan.failing.systems \
/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).