emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Cache must be active error
Date: Mon, 3 Jul 2023 10:08:02 +0700	[thread overview]
Message-ID: <u7te2k$l55$1@ciao.gmane.io> (raw)
In-Reply-To: <87wmzinr76.fsf@yandex.com>

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) early to the load-path in order to compile new
> org-mode versions on the fly without closes emacs.

You may try to add

(message "org? %S" (featurep 'org))

before the line adding Org to load path. Check the *Messages* buffer 
that it reports "nil" to ensure that Org is not loaded through some 
dependencies.

When pulled commits includes changes related to macros, .elc files 
affected by macro expansions must be removed before compilation. 
*Incremental* builds may result in inconsistent code. Emacs developers 
prefer fast, but sometimes incorrect builds and they are rather 
skeptical in relation to proper support of incremental builds.

Without removing *.elc files functions like `byte-recompile-directory' 
and `batch-byte-compile' may produce files that uses old macro versions.



  reply	other threads:[~2023-07-03  3:09 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 [this message]
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='u7te2k$l55$1@ciao.gmane.io' \
    --to=manikulin@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).