Samuel Wales <[email protected]> writes: > that this could cause buffer corruption was new to me and gives this > more urgency. could the error message be changed to point this out?
To be fair, corruption is very unlikely. > in bugfix on bookworm backports emacs, i get various errors and > glitches relatively frequently, but i do not have a recipe for repro, > just a combination of packages that is related to a big subset of the > bugs. > > folding is a frequent trigger. visual line is frequently in the bt. > manual filling with m-q is not a frequent trigger. > i also get glitches in folding that do not produce errors. > > i am limited in computer use. i have not been able to try a different > version of org or emacs. compiling a new emacs is not feasible. i > used to use org master [now main], but scaled back to maint [now > bugfix] for reducing impact. Given your circumstances, I recommend (setq org-element-use-cache nil) This will likely get rid of many errors. If not, please let me know. > i can also offer the observation that many [but definitely not all] > seem related to jit-lock, and among those, most [but not all] seem > related to the [superb] combination as follows: > (auto-fill-mode -1) This is the default, so not unique to you. > (visual-line-fill-column-mode +1) AFAIK, this just changes the fringes - should not cause problems. > (visual-wrap-prefix-mode +1) This one might theoretically do something, yes. It calls adaptive-fill-function frequently that triggers Org parser. -- Ihor Radchenko // yantar92, Org mode maintainer, 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>
