to...@tuxteam.de writes: >> Patches adding org-persist an ability to maintain caches in >> project/current directory will be welcome. > > That's fine -- but note that I just offered *one* example. Playing > whac-a-mole with every single reason someone doesn't want Emacs to > dump uncontrolled stuff to the file system doesn't look (to me) like > the right thing to do. Thus the crowbar :)
Org does dump a lot of stuff onto file system even without org-persist. For example, babel code evaluation writes files to temp directory. Is it ok in your book? > I still don't see why a cache has to be persistent *beyond* the need > to speed up things across sessions. For those not needing that > speedup, it should be a no-brainer to disable it. Agree. You are indeed free to disable the parser cache specifically. This is what `org-element-cache-persistent' user option is for. > Everything else has, to me, an "architecture smell". But that's > probably me :) org-persist has been written specifically to make "Org dumping staff onto file system" in more controlled way. So, yes, it is architecture library. -- 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>
