From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: gerd.moellmann@gmail.com, matt@rfc20.org, 58342@debbugs.gnu.org,
mail@andreas-politz.de
Subject: bug#58342: 29.0.50; noverlay branch is O(N) for important calls
Date: Fri, 07 Oct 2022 16:57:18 +0300 [thread overview]
Message-ID: <83sfjzn3cx.fsf@gnu.org> (raw)
In-Reply-To: <jwvpmf37o4f.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Fri, 07 Oct 2022 09:36:50 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: matt@rfc20.org, bug-gnu-emacs@gnu.org, mail@andreas-politz.de,
> gerd.moellmann@gmail.com
> Date: Fri, 07 Oct 2022 09:36:50 -0400
>
> Eli Zaretskii [2022-10-07 10:09:39] wrote:
> >> [ Site note: `previous-overlay-change` is probably not very important in
> >> practice, but `next-overlay-change` OTOH is indeed important because
> >> it's used during redisplay.
> > previous-overlay-change is also called by redisplay (but I didn't see
> > how frequently), at least if you look at the code from the static
> > analysis POV.
>
> Do you happen to know via which path it can be called (beside the obvious
> ones when the redisplay ends up calling ELisp, such as via jit-lock)?
pos_visible_p
-> previous-single-char-property-change
-> previous-char-property-change
-> previous-overlay-change
Also:
set_point_both
-> previous-char-property-change
-> previous-overlay-change
next prev parent reply other threads:[~2022-10-07 13:57 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 [this message]
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
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=83sfjzn3cx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58342@debbugs.gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=mail@andreas-politz.de \
--cc=matt@rfc20.org \
--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).