Re: Cache must be active error

2023-07-03 Thread Colin Baxter
> Ihor Radchenko writes: > Colin Baxter writes: >> 1. emacs -q 2. eval in scratch buffer (add-to-list >> 'load-path (expand-file-name "~/path/to/git/org-mode/lisp")) >> 3. M-x org-agenda 4. Enter m 5. "Cache must be active" now >> appears in echo area >> >> Am

Re: Cache must be active error

2023-07-03 Thread Ihor Radchenko
Colin Baxter writes: > 1. emacs -q > 2. eval in scratch buffer >(add-to-list 'load-path (expand-file-name "~/path/to/git/org-mode/lisp")) > 3. M-x org-agenda > 4. Enter m > 5. "Cache must be active" now appears in echo area > > Am I seeing a new git/org-mode feature or a bug? A can reprodu

Re: Cache must be active error

2023-07-03 Thread Colin Baxter
> Max Nikulin writes: > On 03/07/2023 14:03, Colin Baxter wrote: >> 2. If I remove all the org files from my emacs-30.50.0 and >> thereby force emacs to use only org-mode from git then I see the >> error. > Have you tried to recompile Org from git or to load it uncompiled

Re: Cache must be active error

2023-07-03 Thread Max Nikulin
On 03/07/2023 14:03, Colin Baxter wrote: 2. If I remove all the org files from my emacs-30.50.0 and thereby force emacs to use only org-mode from git then I see the error. Have you tried to recompile Org from git or to load it uncompiled? Concerning mixed-version loading. M-x org-version when

Re: Cache must be active error

2023-07-03 Thread Colin Baxter
> Max Nikulin writes: > On 03/07/2023 00:44, Colin Baxter wrote: >>> Ihor Radchenko writes: >> > Just for context, the new version `org-element-cache-map' uses >> a > new macro `org-element-with-enabled-cache' that temporarily > >> enabled cache for the duration of `or

Re: Cache must be active error

2023-07-02 Thread Max Nikulin
On 03/07/2023 00:44, Colin Baxter wrote: Ihor Radchenko writes: > Just for context, the new version `org-element-cache-map' uses a > new macro `org-element-with-enabled-cache' that temporarily > enabled cache for the duration of `org-element-cache-map'. I add org-mode (from git

Re: Cache must be active error

2023-07-02 Thread Colin Baxter
8<---cut here---start->8--- >> Debugger entered--Lisp error: (error "Cache must be active.") >> (signal error ("Cache must be active.")) (error "Cache must be >> active.") (org-element-cache-map #f(c

Re: Cache must be active error

2023-07-02 Thread Ihor Radchenko
ror: (error "Cache must be active.") > (signal error ("Cache must be active.")) > (error "Cache must be active.") > (org-element-cache-map #f(compiled-function (el) #)) Just for context, the new version `org-element-cache-map' uses a new macro `org-e

Re: Cache must be active error

2023-07-02 Thread Colin Baxter
ugger output on the error is: --8<---cut here---start----->8--- Debugger entered--Lisp error: (error "Cache must be active.") (signal error ("Cache must be active.")) (error "Cache must be active.") (org-element-cache-map #

Re: Cache must be active error

2023-07-02 Thread Ihor Radchenko
Colin Baxter writes: > I now find that when I enter `m' to match an agenda TAG/PROP/TODO, I get > an error telling me that the "cache must be active". This error is new > today and I assume the result of commit 948c89644. > > I have > > (setq org-element-use-cache nil) > (setq org-element-cache-p

Cache must be active error

2023-07-02 Thread Colin Baxter
I now find that when I enter `m' to match an agenda TAG/PROP/TODO, I get an error telling me that the "cache must be active". This error is new today and I assume the result of commit 948c89644. I have (setq org-element-use-cache nil) (setq org-element-cache-persistent nil) Is there a solution