From: Eli Zaretskii <eliz@gnu.org>
To: Yuan Fu <casouri@gmail.com>
Cc: acm@muc.de, 59738@debbugs.gnu.org
Subject: bug#59738: c-ts-mode is slow with large buffers.
Date: Sun, 11 Dec 2022 09:25:04 +0200 [thread overview]
Message-ID: <83lenev1v3.fsf@gnu.org> (raw)
In-Reply-To: <E8E454C2-5E41-4E85-BE26-962DD6FD6378@gmail.com> (message from Yuan Fu on Sat, 10 Dec 2022 15:14:27 -0800)
> From: Yuan Fu <casouri@gmail.com>
> Date: Sat, 10 Dec 2022 15:14:27 -0800
> Cc: Eli Zaretskii <eliz@gnu.org>,
> 59738@debbugs.gnu.org
>
> Querying time (thus fontification time) increases as the buffer size increases, even if we limit the range of the query to a fixed region (which is what we do in tree-sitter font-lock). This is unlike c-mode, where fontifying a region takes the same amount of time regardless of the buffer size.
The last sentence is inaccurate: sometimes CC Mode must look far
beyond the fixed region which jit-lock.el asks it to fontify. AFAIR,
that is mainly to figure out the syntactical context of the portion of
the buffer that needs to be fontified.
next prev parent reply other threads:[~2022-12-11 7:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 11:50 bug#59738: c-ts-mode is slow with large buffers Alan Mackenzie
2022-12-03 10:37 ` Yuan Fu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-07 4:56 ` Yuan Fu
2022-12-07 17:23 ` Eli Zaretskii
2022-12-08 0:40 ` Yuan Fu
2022-12-08 20:37 ` Eli Zaretskii
2022-12-10 21:34 ` Alan Mackenzie
2022-12-10 23:14 ` Yuan Fu
2022-12-11 7:25 ` Eli Zaretskii [this message]
2022-12-11 13:22 ` Alan Mackenzie
2022-12-11 16:38 ` Dmitry Gutov
2022-12-11 6:45 ` Eli Zaretskii
2022-12-11 17:13 ` Alan Mackenzie
2022-12-11 17:38 ` Eli Zaretskii
2022-12-11 18:39 ` Alan Mackenzie
2022-12-11 19:14 ` Eli Zaretskii
2022-12-13 1:20 ` Stefan Kangas
2022-12-07 14:34 ` Eli Zaretskii
2022-12-07 14:58 ` Eli Zaretskii
2022-12-07 15:46 ` Alan Mackenzie
2023-01-07 23:08 ` Yuan Fu
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=83lenev1v3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59738@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=casouri@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.