From: "Fraga, Eric" <e.fraga@ucl.ac.uk>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: org-persist files in /tmp
Date: Wed, 21 Dec 2022 15:59:33 +0000 [thread overview]
Message-ID: <87a63g21ej.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87tu1ovlsn.fsf@localhost> (Ihor Radchenko's message of "Wed, 21 Dec 2022 15:06:16 +0000")
On Wednesday, 21 Dec 2022 at 15:06, Ihor Radchenko wrote:
> If you run something like make test or emacs -Q + org, it is expected.
> These are throwaway directories used by org-persist for emacs -Q.
I am not explicitly running either of those (at the moment).
I wonder if this is somehow related to native compilation or some other
post-build processes as I have built Emacs twice from git today (and I
always update org when I build Emacs) and these directories have
appeared soon thereafter (I think).
> Do we need to care about cleaning up /tmp?
Maybe not but I do use /tmp for some things and having tens of these
directories does clutter things up a bit. I'm happy to ignore but was
curious as to why they were there at all.
Thank you,
eric
--
: Eric S Fraga, with org release_9.6-124-g036cc0 in Emacs 30.0.50
next prev parent reply other threads:[~2022-12-21 16:00 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 [this message]
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
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=87a63g21ej.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).