From: Ihor Radchenko <yantar92@posteo.net>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: Visuwesh <visuweshm@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Daniel Mendler <mail@daniel-mendler.de>,
emacs-devel@gnu.org
Subject: Re: [elpa] externals/org-modern 0043e584db: Use `display ""` for hiding instead of `invisible t`
Date: Mon, 05 Dec 2022 11:35:41 +0000 [thread overview]
Message-ID: <87y1rmdqwi.fsf@localhost> (raw)
In-Reply-To: <87sfhzoa23.fsf@gmail.com>
Kévin Le Gouguec <kevin.legouguec@gmail.com> writes:
> * org-fold-core-style is 'text-properties by default,
Yes
> * ISTR a bug-gnu-emacs thread where overlay performance was improved, so
> I wondered if Org 9.6 might revert to overlays by default and make the
> new backend opt-in,
We might, after we drop support for Emacs <29 and also implement "new
features" for overlays.
> * then again ORG-NEWS advertises "new features" with the new backend, so
> it's not just a matter of performance I guess?
Yup. I added, for example, auto-unfolding broken syntax elements (when
you, say, edit folded :drawer:... to become drawer:, its contents is
unfolded).
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2022-12-05 11:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166983107217.27025.10929395413721986131@vcs2.savannah.gnu.org>
[not found] ` <20221130175752.70424C00B0F@vcs2.savannah.gnu.org>
2022-11-30 19:55 ` [elpa] externals/org-modern 0043e584db: Use `display ""` for hiding instead of `invisible t` Stefan Monnier
2022-12-01 2:28 ` Visuwesh
2022-12-01 7:30 ` Kévin Le Gouguec
2022-12-05 11:35 ` Ihor Radchenko [this message]
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=87y1rmdqwi.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=kevin.legouguec@gmail.com \
--cc=mail@daniel-mendler.de \
--cc=monnier@iro.umontreal.ca \
--cc=visuweshm@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 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.