From: Nicolas Goaziou <firstname.lastname@example.org>
To: Ihor Radchenko <email@example.com>
Cc: firstname.lastname@example.org, "Kévin Le Gouguec" <email@example.com>
Subject: Re: [9.4] LOGBOOK visibility
Date: Sat, 04 Jul 2020 10:08:17 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <87r1ts3s8r.fsf@localhost> (Ihor Radchenko's message of "Sat, 04 Jul 2020 10:53:56 +0800")
Ihor Radchenko <email@example.com> writes:
> There used to be several types of overlays for headline folding, drawer
> folding, and block folding. One of the recent commits made all the
> overlays use headline type. As a result all the overlays are merged into
> a single overlay upon folding. This was done to reduce the total number
> of overlays present in an org buffer, which degrades Emacs performance
> on huge org files (see the discussion in ).
> What you observe is a consequence of that change. Now, all the drawer
> overlays are destroyed when you fold a heading. Isearch would
> only see a single huge overlay and unfold it alltogether.
For completeness, at the beginning drawers and outline shared the same
At some point during 9.X development, I gave drawers their own
invisibility value. It provided an overall nicer behaviour, but also
introduced some serious slowdown in large files.
Recently, as pointed out by Ihor, I switched drawers back to their
initial state, i.e., they now share the same invisibility value as the
outline. At least, Org on very large files is slightly more manageable,
but the behaviour is less nice. With overlays, you can't have your cake
and eat it too.
> I am currently working on a patch to rewrite the whole folding system.
> Your issue should disappear once it is applied.
Yes, hopefully, switching to text properties will get us out of this sad
next prev parent reply other threads:[~2020-07-04 8:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 10:19 [9.4] LOGBOOK visibility Kévin Le Gouguec
2020-07-03 13:47 ` Kévin Le Gouguec
2020-07-03 18:17 ` Kévin Le Gouguec
2020-07-04 2:53 ` Ihor Radchenko
2020-07-04 4:57 ` Ihor Radchenko
2020-07-04 8:03 ` Kévin Le Gouguec
2020-07-04 8:08 ` Nicolas Goaziou [this message]
2020-07-04 8:28 ` Kévin Le Gouguec
2020-07-04 11:18 ` Ihor Radchenko
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).