From: Colin Baxter <m43cap@yandex.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Cache must be active error
Date: Sun, 02 Jul 2023 18:21:47 +0100 [thread overview]
Message-ID: <871qhqp6tw.fsf@yandex.com> (raw)
In-Reply-To: <87o7ku8em9.fsf@localhost> (Ihor Radchenko's message of "Sun, 02 Jul 2023 16:25:34 +0000")
>>>>> Ihor Radchenko <yantar92@posteo.net> writes:
> Colin Baxter <m43cap@yandex.com> 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-persistent nil)
> This should not matter and should not cause the error. Please
> provide more details.
The debugger 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 #f(compiled-function (el) #<bytecode 0xb3290e9>))
(org-get-buffer-tags)
(org-make-tags-matcher nil)
(org-tags-view nil)
(funcall-interactively org-tags-view nil)
(call-interactively org-tags-view)
(org-agenda nil)
(funcall-interactively org-agenda nil)
(call-interactively org-agenda nil nil)
(command-execute org-agenda)
--8<---------------cut here---------------end--------------->8---
There is an odd feature. If I reload org-mode on a org buffer,
using "C- C-x !" then the error vanishes on using "C-c C-a m". If I
launch a new emacs (28.2 or 30.50.0) then the error returns and only
vanishes if I reload org-mode again.
Colin Baxter.
next prev parent reply other threads:[~2023-07-02 17:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 16:13 Cache must be active error Colin Baxter
2023-07-02 16:25 ` Ihor Radchenko
2023-07-02 17:21 ` Colin Baxter [this message]
2023-07-02 17:29 ` Ihor Radchenko
2023-07-02 17:44 ` Colin Baxter
2023-07-03 3:08 ` Max Nikulin
2023-07-03 7:03 ` Colin Baxter
2023-07-03 7:30 ` Max Nikulin
2023-07-03 12:23 ` Colin Baxter
2023-07-03 12:32 ` Ihor Radchenko
2023-07-03 14:18 ` Colin Baxter
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=871qhqp6tw.fsf@yandex.com \
--to=m43cap@yandex.com \
--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).