From: Charles Millar <millarc@verizon.net>
To: emacs-orgmode@gnu.org
Subject: Re: Release 9.6
Date: Thu, 1 Dec 2022 19:32:45 -0500 [thread overview]
Message-ID: <350b119f-9e70-6480-4481-19b0e6281e6b@verizon.net> (raw)
In-Reply-To: <86tu2eg0us.fsf@gmail.com>
On 12/1/22 18:10, Tim Cross wrote:
>
> Max Nikulin <manikulin@gmail.com> writes:
>
>> On 29/11/2022 13:58, Bastien wrote:
>>> Last but not least: thanks to Ihor his
>>> truly amazing work and for being the de facto maintainer.
>>
>> I think, Ihor's role in this release is crucial. He spent a lot of time fixing bugs and
>> reviewing patches, not to mention the org-fold framework to overcome performance
>> limitation of overlays (the latter has been recently addressed in Emacs though).
>
> I agree. The amount of time and effort Ihor has put into org mode is
> both crucial and hugely appreciated.
>
> One question I do have is with respect to the new folding code, the
> changes in Emacs to improve overlay performance and the correct way
> forward.
>
> On one hand, it was an immense amount of work for Ihor to implement a
> better performing solution and something I'm sure those with large org
> files will appreciate. However, on the other hand, I guess it also puts
> a greater burden from a maintenance perspective on org maintainers as
> org is now using its own unique approach to hiding/showing content
> (folding).
>
> Has anyone done any comparisons between the new overlay implementation
> in Emacs 29 and the new folding approach in org 9.6? Is there still
> sufficient performance benefit with org's approach over using Emacs
> overlays or do we need to seriously consider changing the default back
> to native Emacs overlays?
>
Is this the cause for the behavior I described a few days ago in
Bug org-cycke fails after "replace-string"
Charlie Millar
P.S. Sorry for the typo
next prev parent reply other threads:[~2022-12-02 0:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 6:58 Release 9.6 Bastien
2022-11-30 15:10 ` Max Nikulin
2022-11-30 16:36 ` Thomas S. Dye
2022-12-01 23:10 ` Tim Cross
2022-12-02 0:32 ` Charles Millar [this message]
2022-12-02 5:06 ` 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=350b119f-9e70-6480-4481-19b0e6281e6b@verizon.net \
--to=millarc@verizon.net \
--cc=emacs-orgmode@gnu.org \
/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).