Max Nikulin writes:
> Ihor, do not try to find greatest common denominator that is suitable
> for everybody. ...
Well. I am not exactly trying to find something suitable for every
single user. But why not to address the concerns as much as possible
when it does not involve too much maintenance
On Sun, Aug 03, 2025 at 11:24:26AM +0700, Max Nikulin wrote:
> On 02/08/2025 21:33, Ihor Radchenko wrote:
> > P.S. I am confused why multiple people are asking to disable cache. Org
> > has been creating ltximg directory since forever and nobody ever asked
> > to "disable" that one.
>
> Ihor, do n
On 02/08/2025 21:33, Ihor Radchenko wrote:
P.S. I am confused why multiple people are asking to disable cache. Org
has been creating ltximg directory since forever and nobody ever asked
to "disable" that one.
Ihor, do not try to find greatest common denominator that is suitable
for everybody.
On Sat, Aug 02, 2025 at 03:48:12PM +, Ihor Radchenko wrote:
[...]
> org-persist has been written specifically to make "Org dumping staff
> onto file system" in more controlled way. So, yes, it is architecture
> library.
Fine, then I have one ring to rule them all :-)
(I just have to make su
Thierry Volpiatto writes:
>> This is how latex previews work. This is how code evaluation works.
>
> Code evaluation? Which code evaluation?
Code blocks. See 16.5 Evaluating Code Blocks section of the manual.
When evaluating src-blocks, Org mode creates files in /tmp
--
Ihor Radchenko // yanta
Ihor Radchenko writes:
> Thierry Volpiatto writes:
>
>>> As it usually goes, advicing functions comes at your own risk. So, no
>>> wonder you encountered problems.
>>
>> No. I hardly see how advicing functions with :override 'ignore may
>> delete a whole directory contents of lisp files, so plea
to...@tuxteam.de writes:
> I still don't see why a cache has to be persistent *beyond* the need
> to speed up things across sessions. For those not needing that
> speedup, it should be a no-brainer to disable it.
+1
--
Thierry
signature.asc
Description: PGP signature
to...@tuxteam.de writes:
>> Patches adding org-persist an ability to maintain caches in
>> project/current directory will be welcome.
>
> That's fine -- but note that I just offered *one* example. Playing
> whac-a-mole with every single reason someone doesn't want Emacs to
> dump uncontrolled stuf
Thierry Volpiatto writes:
>> As it usually goes, advicing functions comes at your own risk. So, no
>> wonder you encountered problems.
>
> No. I hardly see how advicing functions with :override 'ignore may
> delete a whole directory contents of lisp files, so please do not
> underestimate this.
On Sat, Aug 02, 2025 at 02:55:37PM +, Ihor Radchenko wrote:
> writes:
>
> >> P.S. I am confused why multiple people are asking to disable cache.
> >
> > Perhaps because there is a need?
>
> >> Org
> >> has been creating ltximg directory since forever and nobody ever asked
> >> to "disable" t
Ihor Radchenko writes:
> Thierry Volpiatto writes:
>
>> I thought I have desactived org-persist for good by advicing ...
>> ...I finally found how to disable this
>> org-persist annoyance by advicing a bunch of functions to 'ignore and
>> disabling some hooks.
>
> As it usually goes, advicing fu
writes:
>> P.S. I am confused why multiple people are asking to disable cache.
>
> Perhaps because there is a need?
>> Org
>> has been creating ltximg directory since forever and nobody ever asked
>> to "disable" that one.
>
> This might have several reasons:
>
> - Not everyone is doing LaTeX w
On Sat, Aug 02, 2025 at 02:33:56PM +, Ihor Radchenko wrote:
[...]
> P.S. I am confused why multiple people are asking to disable cache.
Perhaps because there is a need?
> Org
> has been creating ltximg directory since forever and nobody ever asked
> to "disable" that one.
This might have s
Thierry Volpiatto writes:
> I thought I have desactived org-persist for good by advicing ...
> ...I finally found how to disable this
> org-persist annoyance by advicing a bunch of functions to 'ignore and
> disabling some hooks.
As it usually goes, advicing functions comes at your own risk. So,
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
---
Charles Choi writes:
> After updating to Emacs 30.1, I now see the error message in *Messages*
>
> Error running timer ‘org-persist--refresh-gc-lock’: (wrong-type-argument
> listp \...)
>
>
> So far running Org seems nominal, but thought I'd report this error
> message anyways.
Sounds like a dup
After updating to Emacs 30.1, I now see the error message in *Messages*
Error running timer ‘org-persist--refresh-gc-lock’: (wrong-type-argument
listp \...)
So far running Org seems nominal, but thought I'd report this error
message anyways.
Remember to cover the basics, that is, what you exp
Visuwesh writes:
>> So much for the idea of readable index file.
>
> It is unfortunate, indeed, since the pp version of the file is really
> handy when looking into org-persist issues. Though, I must mention that
> the slowness reported in OP is compounded by my fairly aggressive CPU
> governor
[சனி ஆகஸ்ட் 10, 2024] Ihor Radchenko wrote:
> Visuwesh writes:
>
>> I am using the async LaTeX preview branch and org-persist-write-all
>> takes a lot of time to finish executing due to the use of pp when saving
>> the index file. Changing org-persist-write:index to not pass a non-nil
>> PP argu
Visuwesh writes:
> I am using the async LaTeX preview branch and org-persist-write-all
> takes a lot of time to finish executing due to the use of pp when saving
> the index file. Changing org-persist-write:index to not pass a non-nil
> PP argument to org-persist--write-elisp-file changes the ex
Christian Moe writes:
> I do have a backup of the org-persist directory if there's anything to
> be learned from it about how this happened (but I'm traveling, and don't
> have much time for forensics at the moment).
I don't think so. Not in this case.
I think that we simply need to do format ch
Fixed: I killed emacs, deleted ~/.cache/org-persist/, and things look
OK after restart.
Sorry, obvious solution, but I wasn't thinking straight last night.
I do have a backup of the org-persist directory if there's anything to
be learned from it about how this happened (but I'm traveling, and d
Hi,
It seems my org-persist cache has somehow been corrupted so that opening
any Org-mode file suddenly causes this odd and severe error:
File mode specification error: (wrong-type-argument listp
£6C?^c)
Retyping the above since the characters may turn out wrong:
(wrong-type-argument listp \27
Uwe Brauer writes:
> I found the culprit, the recently installed org-real pkg.
>
> I uninstalled it and everything was back to normally.
Hmm. I suspect that org-real might not be the problem by itself. Rather
you may load it too early and pull-in built-in org.
Best,
Ihor
>>> "UB" == Uwe Brauer writes:
> In connection with my earlier bug report, here is the backtrace when starting
> emacs
> Debugger entered--Lisp error: (void-function org-file-name-concat)
> (void-variable org-descriptive-links)
> You should still send this bug report.
I found the culprit, t
In connection with my earlier bug report, here is the backtrace when starting
emacs
Debugger entered--Lisp error: (void-function org-file-name-concat)
org-file-name-concat("/home/oub/.cache" "org-persist/")
byte-code("\301\302\303 \304\1!\203\16\0\10\202\17\0\211\262\1\305\"!\207"
[user-emac
Samuel Wales writes:
> 20051 135025 938122 other--a.org
>
> this is a smallish to middling file for me. my largest is 4x larger.
> i haven't gotten new org to work yet so i haven't revisited this yet.
This is odd. It only takes 2 sec to write caches for my largest 15Mb
file. Though I have SSD.
20051 135025 938122 other--a.org
this is a smallish to middling file for me. my largest is 4x larger.
i haven't gotten new org to work yet so i haven't revisited this yet.
On 12/24/21, Ihor Radchenko wrote:
> Samuel Wales writes:
>
>> this reproduces most or all of the time. idk if it is uefu
Samuel Wales writes:
> this reproduces most or all of the time. idk if it is ueful to
> anybody, but i thought i would post it in case it is instantly
> recognizable.
>
> emacs 25. latest 9.5 org main.
>
> Debugger entered--Lisp error: (quit)
> read(#)
> org-persist-read(org-element--cache
this reproduces most or all of the time. idk if it is ueful to
anybody, but i thought i would post it in case it is instantly
recognizable.
emacs 25. latest 9.5 org main.
Debugger entered--Lisp error: (quit)
read(#)
org-persist-read(org-element--cache #)
org-mode()
set-auto-mode-0(org-m
30 matches
Mail list logo
