On Monday, July 8th, 2024 at 11:45 AM, Ihor Radchenko <yanta...@posteo.net> wrote:
> Michael Mauger michael.mau...@protonmail.com writes: > > > This bug has been difficult to reproduce but several people have > > encountered it, or symptoms of it. Most recently, there has been this > > thread on Reddit: > > https://www.reddit.com/r/emacs/comments/1drxsz6/tangled_0_code_blocks_from_filename_problem/ > > Just encountered it again. :( The recipe is still not obvious but I'm trying to find one... (This time got the "\..." version) > > After some poking around I started getting failure when I tried to > > reopen an Org file or ran `normal-mode' on it. Shutting down emacs > > and restarting cleared the issue. When the issue arose when reopening > > the file within a session, the backtrace was pointing to` plistp' failing in > > `org-persist-read'. When I looked at the persist index there were > > entries like: > > > > (:container > > ((elisp org-element--headline-cache) (elisp org-element--cache) > > (version "2.3")) > > :persist-file "49/605653-361a-49a4-a000-47db8d522096" :associated > > (:hash "aa1176747642fdac45aaf96095a88367" :file > > "/home/michael/Projects/my-config/emacs/my-org.org" :inode > > 2554490) > > :expiry 30 :last-access 1719791738.4428508 :last-access-hr > > "2024-06-30T19:55:38-0400" ...) > > > > (Note: the "..." in the last entry; sometimes it showed up as "\...".) > > > This is curious. May it be that you have non-default value of > `pp-default-function'? > I don't touch `pp-default-function' and I've confirmed that it is set to `pp-fill' in my instance. > -- > Ihor Radchenko // yantar92, > Org mode contributor, Thanks for your attention.
