emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Esa Palosaari <esa.palosaari@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] visibility cycling does not work because org-element--cache-active-p defined later than it is used in org-element.el
Date: Thu, 01 Sep 2022 15:14:10 +0800	[thread overview]
Message-ID: <87czcfo9bx.fsf@localhost> (raw)
In-Reply-To: <CAN4JR0UiTtRKJK8zwrM4wo7YTVY70a6M6kY83SkQKM_TUkO5yw@mail.gmail.com>

Esa Palosaari <esa.palosaari@gmail.com> writes:

> The expectation is that using TAB cycles subtree visibility. What in
> fact happens is nothing but a "function definition is void:
> org-element--cache-active-p" error is shown in the minibuffer.
>
> The bug is a "function definition void" error when using tabulator
> for subtree cycling on macOS using ARM [9.5.4 (9.5.4-g202744 @
> /Users/esapalosaari/.emacs.d/straight/build/org/)]. The fix is to move
> the function definition (defun org-element--cache-active-p) e.g. to line
> 4128 in org-element.el before it is used by other parts of the code.

`org-element--cache-active-p' function is defined as long as you load
Org correctly. You are likely experiencing "mixed" Org installation when
parts of built-in Org mode are loaded together with the newer files from
Org. Please make sure that you have (straight-use-package 'org) early in
your config.

-- 
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92


      reply	other threads:[~2022-09-01  7:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-31 11:53 [BUG] visibility cycling does not work because org-element--cache-active-p defined later than it is used in org-element.el Esa Palosaari
2022-09-01  7:14 ` Ihor Radchenko [this message]

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=87czcfo9bx.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=esa.palosaari@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).