Rudolf Adamkovič writes:
> Ihor Radchenko writes:
>
>> Fixed, on bugfix.
>> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=5ffb2675f
>
> FYI: A typo, 's/has/hash/'.
>
> (Optionally, also 's/anyway //'.)
Thanks!
Fixed
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?
Ihor Radchenko writes:
> Fixed, on bugfix.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=5ffb2675f
FYI: A typo, 's/has/hash/'.
(Optionally, also 's/anyway //'.)
Rudy
--
"The whole science is nothing more than a refinement of everyday
thinking." --- Albert Einstein, 1879-1
> From: Ihor Radchenko
> Cc: emacs-orgmode@gnu.org
> Date: Thu, 27 Jun 2024 10:11:46 +
>
> Eli Zaretskii writes:
>
> > . set your locale's codeset to something other than UTF-8
> > . type into *scratch*:
> >
> > (insert "* heading\n(")
> > (org-mode)
> > (hs-minor-mode)
> > (hs-hide-all
Eli Zaretskii writes:
> . set your locale's codeset to something other than UTF-8
> . type into *scratch*:
>
> (insert "* heading\n(")
> (org-mode)
> (hs-minor-mode)
> (hs-hide-all)
>
> . mark the region around these 4 sexps and type "M-x eval-region"
> . observe the popup *Warning* windo
Here's one example where org-persistent (I think) triggers an annoying
select-safe-coding-system popup because it is trying to cache
something behind user's back:
. set your locale's codeset to something other than UTF-8
. type into *scratch*:
(insert "* heading\n(")
(org-mode)
(hs-minor-mode
> > A user has somefile.org which contains some headers marked with the
> > "crypt" tag. Only those headers are encrypted. The org-element cache
> > may now cache the whole file, including the encrypted headers (this is
> > ok). Now the user temporarily decrypts the encrypted header, works on
> > i
Daniel Clemente writes:
> Thanks. I'm not sure about the "unless" part here:
>
>> Persisting the cache to disk […]
>> It is not recommended if the Org files
>> include sensitive data, unless the data is encrypted via `org-crypt'.")
>
> I first mentioned org-crypt because users of org-crypt may be
>
> Thanks!
> I am attaching tentative patch that improve the documentation. I hope
> that it clarifies things for you.
>
>
Thanks. I'm not sure about the "unless" part here:
> Persisting the cache to disk […]
> It is not recommended if the Org files
> include sensitive data, unless the data is
Eli Zaretskii writes:
>> Eli Zaretskii writes:
>>
>> >> I was referring to some kind of global option that defines cache
>> >> directory, data directory, etc. Something akin XDG.
>> >
>> > We already have xdg-cache-home (and a few others in xdg.el). Is that
>> > what you meant?
>>
>> Yes, exc
Colin Baxter writes:
> This what I cannot understand. If the user never uses latex preview why
> cannot the latex preview cache be disabled? I don't want to go on and on
> and become a bore - I've said my piece and I will be silent from now
> on.
I believe that we have some kind of misunderstand
> Ihor Radchenko writes:
> Eli Zaretskii writes:
>> Let me clarify. In the scenario in which I found out about Org
>> caching, I didn't use latex-preview, not at all
> Sure. Org uses multiple caches. You encountered the one created
> by parser. The parser cache in
Eli Zaretskii writes:
> Let me clarify. In the scenario in which I found out about Org
> caching, I didn't use latex-preview, not at all
Sure. Org uses multiple caches.
You encountered the one created by parser. The parser cache in
particular can be disabled. But not the latex preview cache
> From: Ihor Radchenko
> Cc: Eli Zaretskii , n142...@gmail.com, emacs-orgmode@gnu.org
> Date: Wed, 19 Jun 2024 10:35:39 +
>
> If you do not use latex-preview or other features that cache their
> results, org-persist should not create any files or directories.
> (It currently does create gc-lo
Colin Baxter writes:
> > 1. not reasonable in a sense that it has downsides compared to
> > what we do now - save latex previews on disk 2. impossible in a
> > sense that we do not have an existing toggle to store cached
> > previews in memory. Such functionality would have to be
> Ihor Radchenko writes:
> Eli Zaretskii writes:
>>> Can we instead store them in memory? Yes, but (1) it will make
>>> Emacs RAM consumption grow constantly and more and more previews
>>> are generated; (2) it will require significant changes in the
>>> Org mode codebase
On Wed, Jun 19, 2024 at 12:06:42AM +0200, Rudolf Adamkovič wrote:
> Ihor Radchenko writes:
>
> > Can we instead store them in memory? Yes, but (1) it will make Emacs RAM
> > consumption grow constantly and more and more previews are generated;
> > (2) it will require significant changes in the Or
Ihor Radchenko writes:
> Can we instead store them in memory? Yes, but (1) it will make Emacs RAM
> consumption grow constantly and more and more previews are generated;
> (2) it will require significant changes in the Org mode codebase.
And, (3) all previews would be lost every time one shuts d
> From: Ihor Radchenko
> Cc: Eli Zaretskii , emacs-orgmode@gnu.org
> Date: Tue, 18 Jun 2024 15:53:18 +
>
> Daniel Clemente writes:
>
> > What's the setting then to disable org-persist? I.e. to disable
> > creating of files like ~/.cache/org-persist/gc-lock.eld
> > Many people seem to want t
Eli Zaretskii writes:
>> Can we instead store them in memory? Yes, but (1) it will make Emacs RAM
>> consumption grow constantly and more and more previews are generated;
>> (2) it will require significant changes in the Org mode codebase.
>
> I understand all that, but if the user wants it, and
> From: Ihor Radchenko
> Cc: n142...@gmail.com, emacs-orgmode@gnu.org
> Date: Tue, 18 Jun 2024 16:25:10 +
>
> Eli Zaretskii writes:
>
> >> It is impossible. We need to store files like latex previews
> >> somewhere. This somewhere is org-persist-directory now.
> >
> > Sorry, I don't underst
Eli Zaretskii writes:
>> It is impossible. We need to store files like latex previews
>> somewhere. This somewhere is org-persist-directory now.
>
> Sorry, I don't understand: why do you need to store them as files?
> Why not keep the previews in buffer(s)?
In Org mode, in order to create latex
Daniel Clemente writes:
>> Nope. "org-persist" directory is not only used by org-element. If some
>> other parts of Org need to cache something, they can also store cache
>> there.
>>
> What's the setting then to disable org-persist? I.e. to disable
> creating of files like ~/.cache/org-persist/g
> > In particular, when setting (setq org-element-cache-persistent nil)
> > org-mode *should not* create an org-persist directory anywhere. And I
> > think it shouldn't activate org-persist timers (it does now) or hooks.
> > The user's preference should be respected.
>
> Nope. "org-persist" directo
Daniel Clemente writes:
> In particular, when setting (setq org-element-cache-persistent nil)
> org-mode *should not* create an org-persist directory anywhere. And I
> think it shouldn't activate org-persist timers (it does now) or hooks.
> The user's preference should be respected.
Nope. "org-p
> From: Ihor Radchenko
> Cc: emacs-orgmode@gnu.org, emacs-de...@gnu.org, michael.albi...@gmx.de
> Date: Sun, 16 Jun 2024 09:05:02 +
>
> Eli Zaretskii writes:
>
> >> I was referring to some kind of global option that defines cache
> >> directory, data directory, etc. Something akin XDG.
> >
Eli Zaretskii writes:
>> I was referring to some kind of global option that defines cache
>> directory, data directory, etc. Something akin XDG.
>
> We already have xdg-cache-home (and a few others in xdg.el). Is that
> what you meant?
Yes, except that `xdg-cache-home' is limited:
1. It cannot
> > Please document the caching features of Org in the manual, including
> > how to turn that off. (I also question the wisdom of turning this on
> > by default without as much as a single request for confirmation from
> > the user.)
> Hmm. What aspect of caching do you want us to document?
> FYI,
> From: Ihor Radchenko
> Cc: emacs-orgmode@gnu.org, emacs-de...@gnu.org, Michael Albinus
>
> Date: Sat, 15 Jun 2024 14:13:03 +
>
> CCing emacs-devel as I'd like to upgrade this discussion to Emacs-wide
> context.
>
> Eli Zaretskii writes:
>
> >> ... I wanted to know what is being cached,
CCing emacs-devel as I'd like to upgrade this discussion to Emacs-wide
context.
Eli Zaretskii writes:
>> ... I wanted to know what is being cached, why, and in what file/directory.
>>
> > ...
>> Would it be possible for Emacs to define a framework for cache/var/data
>> locations? Such framewor
Ihor Radchenko writes:
>> The emacs-internal encoding is not binary. In almost all the cases it
>> is indistinguishable from utf-8-unix. It differs where a buffer
>> includes characters outside of the Unicode codespace. The usual
>> practice in Emacs is that files holding internal data use
>>
> From: Ihor Radchenko
> Cc: emacs-orgmode@gnu.org
> Date: Sat, 15 Jun 2024 12:47:29 +
>
> Eli Zaretskii writes:
>
> >> I am not convinced that we have to do it.
> >
> > That's too bad. When a user finds out about this caching, how do you
> > propose that he/she looks for the information a
Eli Zaretskii writes:
>> I am not convinced that we have to do it.
>
> That's too bad. When a user finds out about this caching, how do you
> propose that he/she looks for the information about it? I wanted to
> know what is being cached, why, and in what file/directory. It took
> me quite som
> From: Ihor Radchenko
> Cc: emacs-orgmode@gnu.org
> Date: Fri, 14 Jun 2024 15:31:28 +
>
> Eli Zaretskii writes:
>
> >> Hmm. What aspect of caching do you want us to document?
> >
> > First and foremost, that it exists, and is turned on by default. The
> > manual is currently completely si
Eli Zaretskii writes:
>> Hmm. What aspect of caching do you want us to document?
>
> First and foremost, that it exists, and is turned on by default. The
> manual is currently completely silent about it.
>
> Next, please document the user options that control this caching, and
> especially those
On 2024-06-14, Ihor Radchenko wrote:
> Eli Zaretskii writes:
>
>> Please document the caching features of Org in the manual, including
>> how to turn that off. (I also question the wisdom of turning this on
>> by default without as much as a single request for confirmation from
>> the user.)
>
>
> From: Ihor Radchenko
> Cc: emacs-orgmode@gnu.org
> Date: Fri, 14 Jun 2024 13:12:42 +
>
> Eli Zaretskii writes:
>
> > I needed to visit org.org, the Org manual, today, and to my surprise
> > saw Emacs writing some data files into the ~/.cache/org-persist/
> > directory. What's more, Emacs
Eli Zaretskii writes:
> I needed to visit org.org, the Org manual, today, and to my surprise
> saw Emacs writing some data files into the ~/.cache/org-persist/
> directory. What's more, Emacs popped a buffer out of the blue telling
> me that it could not safely encode the data written to (I pres
37 matches
Mail list logo
