From: Ihor Radchenko <yantar92@gmail.com>
To: Sharon Kimble <boudiccas@skimble09.plus.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: ?bug in org-fold-core
Date: Thu, 04 Aug 2022 16:50:01 +0800 [thread overview]
Message-ID: <87iln8gzpi.fsf@localhost> (raw)
In-Reply-To: <87bkt0tovf.fsf@skimble09.plus.com>
Sharon Kimble <boudiccas@skimble09.plus.com> writes:
> I've just updated to 'Org mode version 9.5.4 (release_9.5.4-706-g4702a7 @ /home/boudiccas/git/org-mode/lisp/)' and I'm getting this error report from org-fold-core (I think) -
>
> =====
> Debugger entered--Lisp error: (error "Calling ‘org-fold-core-region’ with missing SPEC")
> signal(error ("Calling ‘org-fold-core-region’ with missing SPEC"))
> error("Calling `org-fold-core-region' with missing SPEC")
> org-fold-core-region(652018 652093 t outline)
> org-cycle-content--text-properties(2)
> org-content(2)
> eval((org-content 2) t)
> #f(compiled-function (var val) "Set local variable VAR with value VAL.\nIf VAR is `mode', call `VAL-mode' as a function unless it's\nalready the major mode." #<bytecode 0x18c3ed15a476992f>)(eval (org-content 2))
> apply(#f(compiled-function (var val) "Set local variable VAR with value VAL.\nIf VAR is `mode', call `VAL-mode' as a function unless it's\nalready the major mode." #<bytecode 0x18c3ed15a476992f>) (eval (org-content 2)))
> hack-one-local-variable(eval (org-content 2))
> hack-local-variables-apply()
> hack-local-variables(ignore-mode-settings)
> org-mode()
This is not a bug. This is a changed behaviour of file-local variables.
Now, they are loaded early before most of the Org setup is done in the
buffer; before folding is configured. Hence, the error.
Note that a proper setting of startup visibility should be done via
#+startup keyword:
#+STARTUP: show2levels
Best,
Ihor
next prev parent reply other threads:[~2022-08-04 8:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 8:05 ?bug in org-fold-core Sharon Kimble
2022-08-04 8:50 ` Ihor Radchenko [this message]
2022-08-04 9:38 ` Sharon Kimble
2022-08-04 9:48 ` Ihor Radchenko
2022-08-04 10:41 ` Sharon Kimble
2022-08-05 2:23 ` Ihor Radchenko
2022-08-05 12:11 ` [SOLVED] " Sharon Kimble
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87iln8gzpi.fsf@localhost \
--to=yantar92@gmail.com \
--cc=boudiccas@skimble09.plus.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.