From: <tomas@tuxteam.de>
To: emacs-orgmode@gnu.org
Subject: Re: How to disable completely org-persist
Date: Sat, 31 Dec 2022 08:10:15 +0100 [thread overview]
Message-ID: <Y6/gV8W0yLAokUlf@tuxteam.de> (raw)
In-Reply-To: <918543159.136216.1672450183934@mail1.libero.it>
[-- Attachment #1: Type: text/plain, Size: 1526 bytes --]
On Sat, Dec 31, 2022 at 02:29:43AM +0100, Angelo Graziosi wrote:
>
> > Il 30/12/2022 18:42 Colin Baxter ha scritto:
> >
> >
> > >>>>> Angelo Graziosi writes:
> >
> > > tomas wrote:
> > >> there is now a defvar `org-element-cache-persistent'
> >
> > > Ah! didn't knew that..
> >
> > > Setting
> >
> > > (setq org-element-cache-persistent nil)
> >
> > > seems to work..
> >
> > Indeed, although I'm not yet convinced that org-persist directories wont
> > eventually start showing up in /tmp!
>
> I fear that sooner or later it will reappear somewhere..
Hm. I'm sure people are accepting patches?
Having persistence "centralised" in an org-persist facility
should make it easier for you (or me) to control what happens.
Otherwise, each exporter might be creating files everywhere.
Perhaps it would make sense to state the goals in more
detail. I can see many "aspects":
- "I don't want my ~/.emacs.d/ littered beyond my explicit
control"
- "I don't have (nor want to have) XDG directories"
- "I don't want things in /tmp" [1]
- "I don't want my Emacs's session state to spill to
persistent media"
What is it what you (or me, or anyone) wants to achieve?
Cheers
[1] Currently I see two directories in /tmp made by my emacs
session: some `babel-...', which seems to be made at Org mode
load (before any babel things are invoked), and `emacs1000'
(I start Emacs as a server, so that's where the socket goes)
--
t
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-12-31 7:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-03 0:19 How to disable completely org-persist Angelo Graziosi
2022-12-03 6:05 ` tomas
2022-12-04 8:25 ` Colin Baxter
2022-12-04 3:33 ` Ihor Radchenko
2022-12-04 11:57 ` Colin Baxter
2022-12-13 13:02 ` Ihor Radchenko
2022-12-15 8:10 ` Ihor Radchenko
2022-12-17 9:52 ` Ihor Radchenko
2022-12-04 9:27 ` Angelo Graziosi
2022-12-04 4:34 ` Ihor Radchenko
2022-12-05 15:47 ` Angelo Graziosi
2022-12-05 17:58 ` Colin Baxter
2022-12-30 12:11 ` Angelo Graziosi
2022-12-30 12:38 ` tomas
2022-12-30 13:35 ` Ihor Radchenko
2022-12-30 13:39 ` tomas
2022-12-30 14:18 ` Ihor Radchenko
2022-12-30 13:04 ` Angelo Graziosi
2022-12-30 17:42 ` Colin Baxter
2022-12-31 1:29 ` Angelo Graziosi
2022-12-31 6:06 ` Ihor Radchenko
2022-12-31 7:10 ` tomas [this message]
2023-01-01 13:42 ` Jean Louis
2022-12-31 17:01 ` Angelo Graziosi
2022-12-04 9:32 ` Angelo Graziosi
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=Y6/gV8W0yLAokUlf@tuxteam.de \
--to=tomas@tuxteam.de \
--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).