Max Nikulin <maniku...@gmail.com> writes: > Ihor, do not try to find greatest common denominator that is suitable > for everybody. ...
Well. I am not exactly trying to find something suitable for every single user. But why not to address the concerns as much as possible when it does not involve too much maintenance burden? In this particular case, it looks like part of the problem is that the cache is global. Some people clearly prefer the cache, if written, to be written alongside the relevant Org file. Such a change is necessary anyway, to address privacy concerns for remove mounts discussed in https://list.orgmode.org/orgmode/cam9alr8fusu0yws1sehrw7syxprjfx-r2juxd_dgvcyvkqc...@mail.gmail.com/ > ... We may > try to discuss what are common use cases and what heuristics may be used > to guess what kind of user started Emacs. Emm. Probably having a defcustom is good enough. We don't even have that now. Heuristics is a possible step after a customization is available. > ... Is it possible to > refrain from writing caches if a file is small enough or if it was > instantly parsed? Maybe it is possible to ask user in a non-distracting > way when some slow operations are detected. Yes, but I am not sure if this is going to solve the problem for users who do not like org-persist writing even a single file. I suggested setting org-element-cache-persistent to nil multiple times in this and other threads, and it does not look like it is sufficient. > The following post suggests that many Emacs packages may write to .emacs.d: > > Re: How to disable completely org-persist. Sun, 1 Jan 2023 16:42:36 +0300. > <https://list.orgmode.org/Y7GNzJUyhzls7Y6S@protected.localdomain> > > Perhaps some Emacs-global configuration may be introduced and users > should not adjust configuration of every file. Just an idea > > ((directories . > ((xdg_cache . t) > (emacs_d . nil) > (tmpdir . nil))) > (packages . > ((org . t) > (t . nil)))) ; disabled for other packages > > Maybe more variants should be allowed: ask, force-disabled... Maybe. But that's something that should be discussed on emacs-devel. By a person prepared to defend this kind of feature in front of Emacs maintainers. Maybe with a patch. -- 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>
