Hi Ihor, On Sun, 23 Apr 2023 at 07:55, Ihor Radchenko <yanta...@posteo.net> wrote:
> Thanks for letting us know about this scenario! Yes, but there's little Emacs/Org can do there, I think. Once the volume is mounted, there's no way to tell it is meant to be treated as an encrypted file. With time I'm learning that non-standard setups, while they may seem attractive at first, come and bite you sooner or later. Not necessarily because they are technically flawed, but because it breaks people's expectations. I do have some unusual partitioning scheme, and sometimes it becomes an uphill battle to avoid leakages. On Emacs alone, I have to take special care of backups, bookmarks (that's now fixed on 29), trash, and now cache. > You can use `org-persist-before-write-hook' to disable writing > selectively. Thanks! That's the one. Though it would be nice if a variable existed for the purpose. `(add-hook 'org-persist-before-write-hook (lambda (&rest _args) t) nil t)' is not our average file local variable. :) > You can refer to the comment in org-persist.el for explanation about the > core concepts about CONTAINER and ASSOCIATED terms. > > Let us know if you have difficulties understanding the commentary or if > you think that things can be improved. I took a closer look at it now, and I think it is clear. But I do have a suggestion. I've seen the use of `org-persist' by `org-element' by default announced in the news file. But I think this would deserve an entry in the manual (as far as I can tell, currently there isn't one, but I'm running built-in on 29, so I might be out of date), letting people know it is enabled by default, and how to opt out, if they want to. As my scenario above shows, there's little hope of being able to cover "all cases", and people must take care of that for themselves within reason. All Org can do is let people know, and on security related issues, better be outspoken than shy. And thank you very much for this nice feature! Best, Gustavo.
