emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: m43cap@yandex.com
Cc: tomas@tuxteam.de, emacs-orgmode@gnu.org
Subject: Re: How to disable completely org-persist
Date: Tue, 13 Dec 2022 13:02:31 +0000	[thread overview]
Message-ID: <875yefcv88.fsf@localhost> (raw)
In-Reply-To: <87tu2bkfm3.fsf@localhost>

Ihor Radchenko <yantar92@posteo.net> writes:

> Colin Baxter <m43cap@yandex.com> writes:
>
>> I too would like a means to disable org-persist. I don't doubt it may be
>> useful for those users with "large" org files with multiply src-blocks,
>> etc., etc., but, for me, I have not found any improvement in
>> performance. As remarked by the OP, the feature should not be
>> default-enabled.
>
> Note that org-persist is not only used to cache parser data for large
> files. For example, exported online images are also cached instead of
> being downloaded on every export. Other things may also be cached in
> future.

Upon further investigation, it looks like we need Org persist all the
time. As temporary storage, at least. In particular, downloading remote
images requires org-persist to store files somewhere. All the times.

> That being said, it should not be a big deal to allow disabling
> org-persist when desired. In fact, org-persist is already auto-disabled
> when using emacs -Q. I can add a user switch on top.

So, we cannot disable org-persist and should not even do it with Emacs
-Q. Instead, we may redirect org-persist-directory to /tmp in some
scenarios. I will look into doing this soon.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  parent reply	other threads:[~2022-12-13 13:03 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 [this message]
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
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=875yefcv88.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=m43cap@yandex.com \
    --cc=tomas@tuxteam.de \
    /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).