From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-persist files in /tmp
Date: Fri, 23 Dec 2022 21:12:52 +0700 [thread overview]
Message-ID: <to4d15$p6v$1@ciao.gmane.io> (raw)
In-Reply-To: <Y6VMIWjTBjkjA4d/@tuxteam.de>
On 23/12/2022 13:35, tomas@tuxteam.de wrote:
> On Thu, Dec 22, 2022 at 11:07:52PM +0700, Max Nikulin wrote:
>> Another idea is to avoid caching of parse result for small files.
>
> I haven't been following along very closely, but seeing the
> involved complexities, I'd appreciate a knob to disable caching
> altogether.
Ihor wrote that org-persist usage is not limited to org-element cache.
Another case is referenced remote files. Perhaps e.g. LaTeX preview
still uses old approach for generated image, but it is rather close case.
I do not mind to have a setting that disables org-persist, but it
requires some amount of work. Its priority unlikely will be high.
If you demonstrate that e.g., when working with encrypted files, their
sensitive content leaks to the cache then it will raise the severity of
the issue. Of course, the always appreciated option is to provide a
patch that consistently makes org-persist optional.
next prev parent reply other threads:[~2022-12-23 14:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 13:18 org-persist files in /tmp Fraga, Eric
2022-12-21 15:06 ` Ihor Radchenko
2022-12-21 15:59 ` Fraga, Eric
2022-12-21 16:07 ` Ihor Radchenko
2022-12-21 17:18 ` William Denton
2022-12-21 18:45 ` Ihor Radchenko
2022-12-22 4:30 ` Greg Minshall
2022-12-22 12:34 ` Ruijie Yu via General discussions about Org-mode.
2022-12-22 14:41 ` Max Nikulin
2022-12-22 15:45 ` Tim Cross
2022-12-22 16:07 ` Max Nikulin
2022-12-23 6:35 ` tomas
2022-12-23 14:12 ` Max Nikulin [this message]
2022-12-23 15:19 ` tomas
2022-12-25 9:32 ` Ihor Radchenko
2022-12-25 9:30 ` Ihor Radchenko
2022-12-25 11:37 ` tomas
2022-12-25 9:28 ` Ihor Radchenko
2022-12-25 9:25 ` Ihor Radchenko
2022-12-22 4:35 ` Tim Cross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='to4d15$p6v$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).