From: Ihor Radchenko <yantar92@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 59996-done@debbugs.gnu.org
Subject: bug#59996: 30.0.50; Overlays section of Elisp manual still states that overlays scale linearly
Date: Tue, 13 Dec 2022 10:42:17 +0000 [thread overview]
Message-ID: <87r0x3d1py.fsf@localhost> (raw)
In-Reply-To: <83cz8ospv0.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> I guess that entire section should be audited for inaccuracies now;
> reviews and patches are welcome.
Another part that requires update:
Emacs stores the overlays of each buffer in two lists, divided around
an arbitrary center position. One list extends backwards through the
buffer from that center position, and the other extends forwards from
that center position. The center position can be anywhere in the
buffer.
-- Function: overlay-recenter pos
This function recenters the overlays of the current buffer around
position POS. That makes overlay lookup faster for positions near
POS, but slower for positions far away from POS.
A loop that scans the buffer forwards, creating overlays, can run
faster if you do ‘(overlay-recenter (point-max))’ first.
‘after-string’/‘before-string’ property description might mention that
string are not displayed if the end/beginning of the overlay is not
displayed for some reason.
Also, it might be worth highlighting that unlike text properties,
overlays advance regardless whether insert or insert-and-inherit is used
to insert the buffer text.
--
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>
next prev parent reply other threads:[~2022-12-13 10:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 9:53 bug#59996: 30.0.50; Overlays section of Elisp manual still states that overlays scale linearly Ihor Radchenko
2022-12-12 13:39 ` Eli Zaretskii
2022-12-13 10:42 ` Ihor Radchenko [this message]
2022-12-14 18:15 ` Eli Zaretskii
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r0x3d1py.fsf@localhost \
--to=yantar92@posteo.net \
--cc=59996-done@debbugs.gnu.org \
--cc=eliz@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.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).