From: Kaushal Modi <kaushal.modi@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: BUG: org cycling regression when using the legacy folding style overlays
Date: Mon, 30 May 2022 23:07:03 -0400 [thread overview]
Message-ID: <CAFyQvY3=a8CvmrKvTtswU0odf2EfoPSiC3XrmwAZJcruw+oqCg@mail.gmail.com> (raw)
In-Reply-To: <87v8tmzir6.fsf@localhost>
On Mon, May 30, 2022 at 7:45 PM Ihor Radchenko <yantar92@gmail.com> wrote:
> Your code__collapse_all_posts block makes use of hide-subtree from
> outline.el. Please, do not use it. outline.el is no longer considered
> compatible with Org. It was not in the past, and even more so now. This
> has been announced in ORG-NEWS.
I read the ORG-NEWS:
> The new folding backend breaks some of the =outline-*= functions that
> rely on the details of visibility state implementation in
> =outline.el=. The old Org folding backend was compatible with the
> =outline.el= folding, but it is not the case anymore with the new
> backend. From now on, using =outline-*= functions is strongly
> discouraged when working with Org files.
It says that the new folding backend won't work with outline.el. But
in this case, I am still using the old backend.
Are the outline.el functions expected to stop working for the old backend too?
I replaced hide-subtree with org-fold-hide-subtree and my subtree
collpasing function seems to work as before even with
org-fold-core-style set to 'overlays. I will update this thread if I
see any issue with that.
Thanks!
next prev parent reply other threads:[~2022-05-31 3:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 23:04 BUG: org cycling regression when using the legacy folding style overlays Kaushal Modi
2022-05-30 23:46 ` Ihor Radchenko
2022-05-30 23:56 ` Kaushal Modi
2022-05-31 5:16 ` Ihor Radchenko
2022-05-31 3:07 ` Kaushal Modi [this message]
2022-05-31 3:20 ` Ihor Radchenko
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='CAFyQvY3=a8CvmrKvTtswU0odf2EfoPSiC3XrmwAZJcruw+oqCg@mail.gmail.com' \
--to=kaushal.modi@gmail.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).