From: Jack Kamm <firstname.lastname@example.org>
Subject: Recent folding issues
Date: Mon, 11 Jul 2022 08:56:40 -0700 [thread overview]
Message-ID: <email@example.com> (raw)
I started noticing a couple issues with folding, after updating my
org-mode in recent months:
1. Inserting text below or above a folded headline will cause it to
unfold. I am not sure if this is an intentional change, but I find the
new behavior confusing -- usually I am trying to enter a new headline,
and the unfolding causes me to lose my context and forget what level I
wanted my new headline to be.
2. When folded, I frequently found multiple headlines to be displayed on
the same line, like so:
* Headline 1...
* Headline 2...* Headline 3...
* Headline 4
Hitting Shift-Tab a few times (org-global-cycle) usually fixed the
After reading ORG-NEWS, I found out about org-fold-core-style, and have
set it to 'overlays, which solved both of my problems.
However, this makes me wonder whether it should be the default
value. The help for it says:
> Can be either ‘text-properties’ or ‘overlays’.
> The former is faster on large files, while the latter is generally
> less error-prone.
Since the latter is less error-prone, shouldn't it be the default? And
then a user can switch the value if they have really large files and
need better performance. It's great that performance is being improved
for large files, but I'm not sure this is ready to be the default yet.
next reply other threads:[~2022-07-11 15:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 15:56 Jack Kamm [this message]
2022-07-12 1:08 ` Recent folding issues Ihor Radchenko
2022-07-12 6:17 ` Jack Kamm
2022-07-12 13:58 ` Ihor Radchenko
2022-07-13 14:50 ` Jack Kamm
2022-07-14 13:40 ` Ihor Radchenko
2022-07-19 13:21 ` Ihor Radchenko
2022-07-23 15:38 ` Jack Kamm
2022-07-12 4:30 ` William Denton
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).