From: Sharon Kimble <boudiccas@skimble09.plus.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: ?bug in org-fold-core
Date: Thu, 04 Aug 2022 10:38:49 +0100 [thread overview]
Message-ID: <87tu6s8i1i.fsf@skimble09.plus.com> (raw)
In-Reply-To: <87iln8gzpi.fsf@localhost> (Ihor Radchenko's message of "Thu, 04 Aug 2022 16:50:01 +0800")
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Ihor Radchenko <yantar92@gmail.com> writes:
> 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
>
Thanks for replying.
I now have this showing in my 'instructions.org'
=====
# -*- coding: utf-8; mode: org -*-
#+STARTUP: show2levels
# #+STARTUP: overview
=====
This file seems to be showing most of the problems, and looking at it in 'org-lint' there are many problems. But this file is just some problems that I've found and their solutions, so it shows the wrong way
to do something and then the correct way. Is it possible for it to have a file-only way of reverting to the old way of 'file-local variables' please? As it currently stands, no org-headings are
shown in the colours that other org-files are showing them, and its giving the appearance of org-mode not reading and displaying it!
Thanks
Sharon.
- --
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
DrugFacts = https://www.drugfacts.org.uk
Debian 11, fluxbox 1.3.7, emacs 29.0.50, org 9.5.4
-----BEGIN PGP SIGNATURE-----
iQJRBAEBCgA7FiEELSc/6QwVBIYugJDbNoGAGQr4g1sFAmLrk6kdHGJvdWRpY2Nh
c0Bza2ltYmxlMDkucGx1cy5jb20ACgkQNoGAGQr4g1sVEg/+P8SaFo8ahnpmiaIX
5Ckv5gS8KFIQOPE3cEX0pHs5d9RTHPJiHhGQ2CodgnqhAExU0ppvK3z4uIkmw6ln
YJoHhd/eLWAt2BpnktJ6TDHDIohdtG8ih8U1re5DqZMASSTPRBgsKhvadYMGHCU3
q5nYgfd26A0TB3i6qRgVPrlaUzGfMTM4TozI0KnuAoOa8IDh7dSRHMusZDsjNpuN
Z8TJN79rXxAkz6lSL5C1cgkykJqm1nG7zPdq09tdPIwuartBrnPsrHmAA6EFDOv2
hYpSh91AORaAV8/sSffyy7IX58DWDL6AQ+HBvWGtuR5f3xLV4mP3MnP3YF44DpTr
HeTdZt4KjPlpZSqcuv36Zko9k2idX1BNWHZCc0e7ZpTAGVP0j+s7qqycejrerZfR
R8L07O4uJ1sSZJJ8tupp9NnQMVpznvF5xxjfq7uG8pbIvM7eKbqpbJWMzea8949P
YM2zxcLa08fk6SeV27riK0Bm4R37ERuaPfZefFyxxsIWD4xH4elQqDQSvxQr7TZl
bv3R9Jm72jM+tEcWzh4dr1re/lErpvKJuWiTcuf5TtUwujY7wOIBSH8oPDxReeWE
GMMrybHjO7dk5TArCMkSGfYrDvgW6M8MB2BFeMeqJxZa8WJFnRkq3/Va1FQkLhGt
eDJF7uaJkx9e2t+OmcWxsI9MT5U=
=4yAA
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2022-08-04 9:42 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
2022-08-04 9:38 ` Sharon Kimble [this message]
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
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=87tu6s8i1i.fsf@skimble09.plus.com \
--to=boudiccas@skimble09.plus.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@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).