From: Ihor Radchenko <yantar92@gmail.com>
To: imymorror wang <jagger.wangzg.2019@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] when open a large org file, emacs get stuck and show a warning "org-element--cache: Unregistered buffer modifications detected"
Date: Wed, 18 May 2022 13:46:26 +0800 [thread overview]
Message-ID: <87k0ajxuj1.fsf@localhost> (raw)
In-Reply-To: <CAGVe721ckg9U=NSy87TigYQ6SQcKd6zwg4h30LgmqDb6m-uWog@mail.gmail.com>
imymorror wang <jagger.wangzg.2019@gmail.com> writes:
>> *Can you please share the exact output of M-x org-version?If you really
>> see 9.5.1, then you likely have a "mixed" Org installationwith some code in
>> your init file first loading built-in Org mode andthen loading the newer
>> version. Such state can cause all kinds of bugs.*
>
>
> You are right. When I Update Org to the latest version *Org mode version
> 9.5.3 (9.5.3-g277897)* . The bug is gone。
Sharing this to the mailing list (it was not in CC).
Best,
Ihor
next prev parent reply other threads:[~2022-05-18 5:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 22:59 [BUG] when open a large org file, emacs get stuck and show a warning "org-element--cache: Unregistered buffer modifications detected" imymorror wang
2022-05-17 16:38 ` William Denton
2022-05-18 3:14 ` Ihor Radchenko
2022-05-18 3:10 ` Ihor Radchenko
[not found] ` <CAGVe721ckg9U=NSy87TigYQ6SQcKd6zwg4h30LgmqDb6m-uWog@mail.gmail.com>
2022-05-18 5:46 ` Ihor Radchenko [this message]
2022-05-19 9:58 ` imymorror wang
2022-05-20 7:55 ` Ihor Radchenko
[not found] ` <CAGVe723h4bBCZsH95=JpQ3gjxGKfT8R0whU6=QvBGybR+Bb7Hw@mail.gmail.com>
[not found] ` <87leuv3bzt.fsf@localhost>
2022-05-21 3:58 ` Fwd: " imymorror wang
2022-05-21 4:11 ` imymorror wang
2022-05-21 4:38 ` Fwd: " Ihor Radchenko
2022-05-21 7:09 ` imymorror wang
2022-05-21 7:26 ` imymorror wang
2022-05-21 7:49 ` Ihor Radchenko
2022-07-18 0:20 ` 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=87k0ajxuj1.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jagger.wangzg.2019@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).