From: Ihor Radchenko <yantar92@gmail.com>
To: Aaron Jensen <aaronjensen@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Unregistered buffer modifications detected [9.5 (9.5-g49e2f6 @ /Users/myuser/.emacs.d/straight/29/straight/build/org/)]
Date: Wed, 03 Nov 2021 19:40:39 +0800 [thread overview]
Message-ID: <87ee7xeabs.fsf@localhost> (raw)
In-Reply-To: <CAHyO48yS2EAJnhiYoK7syjb1_Fbfxcv2A0fk4t5RFzTLj1hSGA@mail.gmail.com>
Aaron Jensen <aaronjensen@gmail.com> writes:
> Here is another that just happened:
> https://gist.github.com/aaronjensen/5294a64f243a306b58062113b9306bab
>
> It's scrubbed of all string data, hopefully not over-scrubbed for you.
Thanks! It was really helpful. The problem was org-roam calling
org-element-parse-buffer frequently. org-element-parse-buffer had a bug
causing element cache corruption. Sometimes, :parent property of cached
elements was set to uncached elements - something cache code does not
expect. Fixed on main now.
Best,
Ihor
next prev parent reply other threads:[~2021-11-03 11:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-30 15:17 [BUG] Unregistered buffer modifications detected [9.5 (9.5-g49e2f6 @ /Users/myuser/.emacs.d/straight/29/straight/build/org/)] Aaron Jensen
2021-10-30 15:39 ` Ihor Radchenko
2021-10-30 16:45 ` Aaron Jensen
2021-10-31 2:07 ` Aaron Jensen
2021-10-31 2:55 ` Ihor Radchenko
2021-10-31 2:48 ` Ihor Radchenko
2021-10-31 3:16 ` Aaron Jensen
2021-11-01 0:38 ` Aaron Jensen
2021-11-01 12:50 ` Ihor Radchenko
2021-11-02 23:19 ` Aaron Jensen
2021-11-02 23:32 ` Aaron Jensen
2021-11-03 11:40 ` Ihor Radchenko [this message]
2021-11-03 11:45 ` Ihor Radchenko
2021-11-03 14:30 ` Aaron Jensen
2021-11-04 3:18 ` Aaron Jensen
2021-11-04 14:12 ` Ihor Radchenko
2021-11-04 17:05 ` Aaron Jensen
2021-11-12 4:25 ` Aaron Jensen
2021-11-14 8:01 ` Ihor Radchenko
2021-11-14 20:10 ` Aaron Jensen
2021-11-17 6:05 ` Aaron Jensen
2021-11-17 12:04 ` Ihor Radchenko
2021-11-18 14:15 ` Aaron Jensen
2021-11-18 14:30 ` Ihor Radchenko
2021-11-17 12:20 ` Max Nikulin
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=87ee7xeabs.fsf@localhost \
--to=yantar92@gmail.com \
--cc=aaronjensen@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).