From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: matt@rfc20.org, yantar92@gmail.com, 57150@debbugs.gnu.org
Subject: bug#57150: 29.0.50; [PATCH] Add test coverage for overlay modification hooks
Date: Wed, 17 Aug 2022 14:51:26 +0300 [thread overview]
Message-ID: <837d37dr5t.fsf@gnu.org> (raw)
In-Reply-To: <E1oO98g-0008JS-3o@fencepost.gnu.org> (message from Richard Stallman on Tue, 16 Aug 2022 22:50:38 -0400)
> From: Richard Stallman <rms@gnu.org>
> Cc: yantar92@gmail.com, matt@rfc20.org, 57150@debbugs.gnu.org
> Date: Tue, 16 Aug 2022 22:50:38 -0400
>
> > The problems with overlays in Emacs are much wider than just Org. Our
> > performance sucks in many cases because of that. Just two examples
> > that were mentioned lately in the "long-line optimizations"
> > discussion: show-paren-mode and isearch-lazy-highlight -- each one of
> > these two is capable of literally bringing Emacs to its knees,
> > response-time wise.
>
> The first question is, should these use text properties instead of
> overlays?
Text properties are less convenient when used for ephemeral
highlighting.
> Are they using many overlays to highlight many potential matches in a
> long buffer?
isearch-lazy-highlight does.
> If so, would it make sense to show, at any time, only those
> that are near point? When you move to a far-away part of the buffer,
> it could add highlighting to the matches near there. But maybe it
> can avoid ever trying to highlight more than a few parts of the buffer.
isearch.el already attempts to do that, but its method of detecting
what's out of the window doesn't work under truncate-lines.
prev parent reply other threads:[~2022-08-17 11:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 4:32 bug#57150: 29.0.50; [PATCH] Add test coverage for overlay modification hooks Matt Armstrong
2022-08-12 4:41 ` Matt Armstrong
2022-08-12 6:19 ` Eli Zaretskii
2022-08-12 17:57 ` Matt Armstrong
2022-08-12 18:53 ` Eli Zaretskii
2022-08-14 4:52 ` Matt Armstrong
2022-08-14 7:15 ` Eli Zaretskii
2022-09-04 21:59 ` Lars Ingebrigtsen
2022-08-13 4:07 ` Ihor Radchenko
2022-08-14 0:44 ` Matt Armstrong
2022-08-15 4:14 ` Ihor Radchenko
2022-08-15 11:26 ` Eli Zaretskii
2022-08-17 2:50 ` Richard Stallman
2022-08-17 10:05 ` Ihor Radchenko
2022-08-17 11:51 ` Eli Zaretskii [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=837d37dr5t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=57150@debbugs.gnu.org \
--cc=matt@rfc20.org \
--cc=rms@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.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).