From: Dmitry Gutov <dgutov@yandex.ru>
To: Alan Mackenzie <acm@muc.de>, Yuan Fu <casouri@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 59738@debbugs.gnu.org
Subject: bug#59738: c-ts-mode is slow with large buffers.
Date: Sun, 11 Dec 2022 18:38:52 +0200 [thread overview]
Message-ID: <fa2a45ba-fe3a-bba8-c4a4-e2d665a48539@yandex.ru> (raw)
In-Reply-To: <Y5XZl+lC1pp05Hxd@ACM>
On 11/12/2022 15:22, Alan Mackenzie wrote:
>> Though I’ll note that tree-sitter would provide other benefits. I don’t
>> know how much time does c-mode spend on analyzing the buffer content
>> when user edits it, ....
> It's quite a lot. Occasionally, it's enough to make the response appear
> a little sluggish. This analysis, time-wise, is less critical than the
> time taken for font locking, though.
If we test a different scenario (font-locking just one screen-ful,
perhaps repeatedly, while the user is typing), which of the steps can
take more time in a large buffer?
next prev parent reply other threads:[~2022-12-11 16:38 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
2022-12-11 13:22 ` Alan Mackenzie
2022-12-11 16:38 ` Dmitry Gutov [this message]
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=fa2a45ba-fe3a-bba8-c4a4-e2d665a48539@yandex.ru \
--to=dgutov@yandex.ru \
--cc=59738@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=casouri@gmail.com \
--cc=eliz@gnu.org \
/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.