From: Matt Armstrong <matt@rfc20.org>
To: Drew Adams <drew.adams@oracle.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Eli Zaretskii <eliz@gnu.org>
Cc: "gerd.moellmann@gmail.com" <gerd.moellmann@gmail.com>,
"mail@andreas-politz.de" <mail@andreas-politz.de>,
"58342@debbugs.gnu.org" <58342@debbugs.gnu.org>
Subject: bug#58342: 29.0.50; noverlay branch is O(N) for important calls
Date: Sat, 08 Oct 2022 16:08:36 -0700 [thread overview]
Message-ID: <878rlp6hhn.fsf@rfc20.org> (raw)
In-Reply-To: <SJ0PR10MB54883A5F0C013B174264DBCAF35E9@SJ0PR10MB5488.namprd10.prod.outlook.com>
Drew Adams <drew.adams@oracle.com> writes:
>> For the potential performance problem with next-overlay-change to appear
>> you need overlays to overlap, so not something like linum or nhexl-mode.
>
> Which is why I mentioned zones.el.
>
> And I don't expect it to be alone in this.
> Overlays can be anywhere.
For what it is worth, the use cases where this bug applies are likely to
be noticeably slow in Emacs today as well.
prev parent reply other threads:[~2022-10-08 23:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 23:25 bug#58342: 29.0.50; noverlay branch is O(N) for important calls Matt Armstrong
2022-10-07 1:12 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-07 7:09 ` Eli Zaretskii
2022-10-07 13:36 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-07 13:57 ` Eli Zaretskii
2022-10-07 14:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-07 15:23 ` Matt Armstrong
2022-10-07 16:51 ` bug#58361: " Andreas Politz
2022-10-07 18:38 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-07 17:11 ` bug#58342: " Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-07 20:37 ` Matt Armstrong
2022-10-07 21:22 ` Drew Adams
2022-10-08 0:27 ` Drew Adams
2022-10-07 21:58 ` Dmitry Gutov
2022-10-08 6:20 ` Eli Zaretskii
2022-10-08 13:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-08 17:24 ` Drew Adams
2022-10-08 23:08 ` Matt Armstrong [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
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=878rlp6hhn.fsf@rfc20.org \
--to=matt@rfc20.org \
--cc=58342@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=mail@andreas-politz.de \
--cc=monnier@iro.umontreal.ca \
/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).