From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 57447@debbugs.gnu.org, Ihor Radchenko <yantar92@gmail.com>
Subject: bug#57447: 28.1.90; Can font-lock stop requesting fontification of invisible text?
Date: Sat, 27 Aug 2022 11:21:11 -0400 [thread overview]
Message-ID: <jwvfshhvhud.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83r112ymjn.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 27 Aug 2022 14:05:00 +0300")
>> > If the size is smaller than the visible portion of the buffer, it will
>> > cause repeated calls to fontification-functions, instead of just one
>> > call. If fontification-functions do their job in approximately linear
>> > time, you shouldn't see any adverse effects, I think. But if each
>> > call to fontification-functions incurs some one-time overhead that is
>> > relatively expensive, the result could be slower redisplay when the
>> > window is scrolled a lot.
>> This may be an issue in some scenarios.
>> I am wondering if something like font-lock-extend-region-functions may
>> be utilized to shrink the fontification boundaries.
> I don't know. Maybe Stefan does.
The short answer is: no.
[ Tho I don't understand how the question relates to the text before
it: reducing the size of a chunk wouldn't reduce the number of times
fontification-functions is called. ]
Stefan
next prev parent reply other threads:[~2022-08-27 15:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-27 5:34 bug#57447: 28.1.90; Can font-lock stop requesting fontification of invisible text? Ihor Radchenko
2022-08-27 7:02 ` Eli Zaretskii
2022-08-27 7:45 ` Ihor Radchenko
2022-08-27 9:18 ` Eli Zaretskii
2022-08-27 10:37 ` Ihor Radchenko
2022-08-27 11:05 ` Eli Zaretskii
2022-08-27 11:11 ` Ihor Radchenko
2022-08-27 11:17 ` Eli Zaretskii
2022-08-27 11:24 ` Ihor Radchenko
2022-08-27 15:21 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-08-27 15:25 ` Eli Zaretskii
2022-08-28 1:23 ` Ihor Radchenko
[not found] ` <jwvtu5wsa21.fsf-monnier+emacs@gnu.org>
[not found] ` <87r10xp07l.fsf@localhost>
[not found] ` <jwvy1v4giz3.fsf-monnier+emacs@gnu.org>
[not found] ` <875yi7o8x3.fsf@localhost>
[not found] ` <jwvmtbjgmrs.fsf-monnier+emacs@gnu.org>
[not found] ` <jwvo7vsb3fz.fsf-monnier+emacs@gnu.org>
[not found] ` <8735d2pghv.fsf@localhost>
2022-09-09 14:52 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvfshhvhud.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=57447@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.