emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: imymorror wang <jagger.wangzg.2019@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [BUG] when open a large org file, emacs get stuck and show a warning "org-element--cache: Unregistered buffer modifications detected"
Date: Tue, 17 May 2022 06:59:39 +0800	[thread overview]
Message-ID: <CAGVe723kntfjnX53d98ka2tbApvduD1juc1PAvjvzvx8D-HJJw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]

  - desktop environment
    - GNU Emacs 29.0.50 (build 2, x86_64-apple-darwin20.4.0, NS
appkit-2022.44 Version 11.3.1 (Build 20E241)) of 2022-01-08
    - Org mode version 9.5.1
  - bug description
    - influence factor
      - a large org file : 11053 lines。1092 headlines。
      - (setq org-startup-folded t)
      - org-indent-mode : (add-hook 'org-mode-hook 'org-indent-mode)
    - My Observation
      - if setting org-startup-folded t , open the large org file, emacs
get stuck, the mouse can't move。
      - if keeping org-startup-folded defaul value(i.e  "showeverything") ,
enable org-indent-mode , open the large org file, get a warning:
        #+begin_quote
        Warning (org-element-cache): org-element--cache: Unregistered
buffer modifications detected. Resetting.
        If this warning appears regularly, please report it to Org mode
mailing list (M-x org-submit-bug-report).
        #+end_quote
      - if keeping org-startup-folded defaul value and disable
org-indent-mode , open the large org file, everything works fine

[-- Attachment #2: Type: text/html, Size: 1190 bytes --]

             reply	other threads:[~2022-05-17 16:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16 22:59 imymorror wang [this message]
2022-05-17 16:38 ` [BUG] when open a large org file, emacs get stuck and show a warning "org-element--cache: Unregistered buffer modifications detected" 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
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=CAGVe723kntfjnX53d98ka2tbApvduD1juc1PAvjvzvx8D-HJJw@mail.gmail.com \
    --to=jagger.wangzg.2019@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).