Not closed.
Gregor Zattler <[email protected]> writes: > yes. The version string still looks > similar: > > Org mode version 10.0-pre (release_9.7.27-1286-g76e4db @ > /home/grfz/src/org-mode/lisp/) > > besides the "10.0-pre" this seems > reasonable. > Therefore I would not know why the > installation would be mixed. There is > also no such warning. Got it. So, you are on main. > But with compiled org I get plenty of > warnings regarding the cache: > ... > ■ Warning (org-element): org-element--cache: (nil) Cached element is > incorrect in YYY.org. (Cache tic up to date: "no") Resetting. This gives a clue. I suspect that you have something in your config that bypasses modification hooks somehow. (I am not sure why this happens only with compiled Org though) > Actually I just started to use org from > elpa in order to get a compiled version, > when I stumbled upon your ping email. > So I switched the load-path sanitation > back to using org from git sources and > did > > git fetch --all; git pull ; make compile info autoloads > > in the org-mode source directory, then > started Emacs anew. Bingo above > warnings. Does the problem happen if you start from "make repro" with clean Emacs + Org? Maybe you can bisect the config. -- 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>
