From: Noboru Ota <me@nobiot.com>
To: Ihor Radchenko <yantar92@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Introducing Org-transclusion
Date: Sat, 06 Nov 2021 11:43:08 +0100 [thread overview]
Message-ID: <87r1btk1j7.fsf@nobiot.com> (raw)
In-Reply-To: <87v91c9fgu.fsf@localhost>
Ihor Radchenko <yantar92@gmail.com> writes:
> I noticed that you are using overlays in text-clone. It may potentially
> cause slowdown in large Org buffers. Of course, it does not mean that
> org-transclusion should not be accepted. Just something that may be
> optimised.
Karl Voit (GitHub user name, novoid) gave me a comment in a similar vein
regarding potential performance issues as follows:
> As far as I understood: when you do have many overlays in deeply nested headings that are collapsed and you scroll over the lines with the collapsed headings, Emacs needs to handle those overlays and therefore is not able to perform a simple line change without issues.
Source:
https://github.com/nobiot/org-transclusion/issues/42#issuecomment-739570395
I personally have never come across such performance issue. Are you
aware of some good test file or something to let other people reproduce
it?
For now, I am inclined to keeping the use of overlays as is. It's
partially because of my psychological inertia and partially because
text-clone makes uses of overlay's properties:
- "Evaporate" property to take care of when to finish text-clone
- Yanking does not copy overlay properties to avoid accidental cloning
If performance issues become more prevalent and it's something I can
address within my skill set, I will be happy to review the use of
overlays, of course.
next prev parent reply other threads:[~2021-11-06 10:44 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-30 11:51 Introducing Org-transclusion Noboru Ota
2021-10-30 12:31 ` Juan Manuel Macías
2021-11-01 9:17 ` Noboru Ota
2021-10-30 13:59 ` Ihor Radchenko
2021-11-01 9:11 ` Noboru Ota
2021-11-01 13:24 ` Ihor Radchenko
2021-11-06 10:43 ` Noboru Ota [this message]
2021-11-08 15:07 ` Ihor Radchenko
2021-11-10 21:09 ` Noboru Ota
2021-11-14 8:22 ` Ihor Radchenko
2021-11-14 9:35 ` Ihor Radchenko
2021-11-01 20:07 ` Thomas Paulsen
2021-11-01 21:01 ` Noboru Ota
2021-11-02 5:17 ` Timothy
2021-11-05 19:53 ` Noboru Ota
2021-11-05 21:56 ` Tim Cross
2021-11-05 23:20 ` Timothy
2021-11-06 10:14 ` Noboru Ota
2021-11-06 10:22 ` Tim Cross
2021-11-06 11:49 ` Noboru Ota
2021-11-05 17:11 ` Uwe Brauer
2021-11-05 19:24 ` Noboru Ota
2021-11-05 20:15 ` Uwe Brauer
2021-11-05 23:02 ` Noboru Ota
2021-11-06 14:01 ` Uwe Brauer
2021-11-06 14:25 ` Ihor Radchenko
2021-11-06 14:54 ` Noboru Ota
2021-11-06 15:49 ` Uwe Brauer
2021-11-07 7:34 ` Ihor Radchenko
2021-11-07 8:07 ` Uwe Brauer
2021-11-07 8:30 ` Ihor Radchenko
2021-11-07 13:25 ` Uwe Brauer
2021-11-07 13:41 ` Ihor Radchenko
2021-11-07 13:56 ` Uwe Brauer
2021-11-05 19:59 ` Noboru Ota
2021-11-05 20:13 ` Uwe Brauer
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=87r1btk1j7.fsf@nobiot.com \
--to=me@nobiot.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).