From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-persist files in /tmp
Date: Thu, 22 Dec 2022 23:07:52 +0700 [thread overview]
Message-ID: <to1vcp$flj$1@ciao.gmane.io> (raw)
In-Reply-To: <86pmcbigmt.fsf@gmail.com>
On 22/12/2022 22:45, Tim Cross wrote:
> Could some of the issues people are concerned about regarding use of
> /tmp be avoided if instead the temporary files were put into ~/.cache?
There is no ~/.cache on Windows, the fallback is ~/.emacs.d. org-persist
files in ~/.emacs.d was the original source of complains. Moreover, I do
not think emacs -q should write to the same places as emacs initialized
in the regular way.
I see a couple of options:
- Remove the directory on exit (taking some care to not prevent quit in
the cases of errors)
- Create the directory lazily. The variable should not be accessed
directly, when some code is going to write a file it should call a
function that creates the directory if it is first call.
Another idea is to avoid caching of parse result for small files.
next prev parent reply other threads:[~2022-12-22 16:37 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 [this message]
2022-12-23 6:35 ` tomas
2022-12-23 14:12 ` Max Nikulin
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='to1vcp$flj$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).