From: Colin Baxter <m43cap@yandex.com>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Cache must be active error
Date: Mon, 03 Jul 2023 13:23:23 +0100 [thread overview]
Message-ID: <87ilb1fakk.fsf@yandex.com> (raw)
In-Reply-To: <u7tte1$1of$1@ciao.gmane.io> (Max Nikulin's message of "Mon, 3 Jul 2023 14:30:08 +0700")
>>>>> Max Nikulin <manikulin@gmail.com> 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?
> Concerning mixed-version loading. M-x org-version when read with
> attention may contain a hint. Other tools are
> `list-load-path-shadows' and
> (ignore (pp (mapcar (lambda (x) (list (car x))) load-history)))
> and search for "org"
I now a recipe:
Either with emacs-28.2 or emacs-30.0.50 do:
1. emacs -q <RET>
2. M-x org-agenda <RET>
3. Enter m
4. "Match:" appears in echo area
However:
1. emacs -q <RET>
2. eval in scratch buffer
(add-to-list 'load-path (expand-file-name "~/path/to/git/org-mode/lisp"))
3. M-x org-agenda <RET>
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? The lisp files in
git/org-mode/lisp were not byte-compiled.
Colin Baxter.
next prev parent reply other threads:[~2023-07-03 12:24 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
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 [this message]
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=87ilb1fakk.fsf@yandex.com \
--to=m43cap@yandex.com \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.com \
/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).