From: Ihor Radchenko <yantar92@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 57447@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#57447: 28.1.90; Can font-lock stop requesting fontification of invisible text?
Date: Sat, 27 Aug 2022 19:11:52 +0800 [thread overview]
Message-ID: <87wnaudjpj.fsf@localhost> (raw)
In-Reply-To: <83r112ymjn.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> then it does not always hold:
>
> How did you collect the BEG and END values? FWIW, I don't see
> anything in jit-lock that enlarges the chunk size, except perhaps in
> the stealth-fontification case, which you didn't activate?
BEG and END in my data are calculated when matching a font-lock-keyword.
BEG is (point) when the keyword function is called and END is the LIMIT.
--
Ihor Radchenko,
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-08-27 11:11 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 [this message]
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
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
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=87wnaudjpj.fsf@localhost \
--to=yantar92@gmail.com \
--cc=57447@debbugs.gnu.org \
--cc=eliz@gnu.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).