From: ronisbr via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Yuan Fu <casouri@gmail.com>
Cc: 60223@debbugs.gnu.org
Subject: bug#60223: 29.0.60; Improve how tree-sitter changes to treesit--font-lock-fast-mode
Date: Wed, 21 Dec 2022 12:59:27 -0300 [thread overview]
Message-ID: <d993fbc8e539624088eb9b3c4ce8abe8@ronanarraes.com> (raw)
In-Reply-To: <813B3BC7-BD3C-4327-A175-DEB43B2EB11E@gmail.com>
Hi Yuan!
Em 2022-12-21 01:17, Yuan Fu escreveu:
> Thanks for the report!
>
> The "fast mode" should be buffer-local, so that particular file
> shouldn’t affect other buffers. Just to make sure, you said that if you
> open print.jl first, all other files are affected?
Sorry for the misunderstanding. Indeed, only print.jl is affected.
The behavior is:
1. If I open `print.jl` as the first file, the fast mode is
activated,
and the buffer shows a very strange font lock. All other buffers
(including Julia files) work as expected.
2. If I open any other Julia file and then I open `print.jl`, the
fast
mode is not activated, and everything works as expected.
> And I agree that the 0.01 second criterion is a crude one, but a long
> string shouldn’t affect the _query_ time, and that string is not long
> at
> all, far from enough to make tree-sitter query to slow down. Let me
> investigate and see what’s the real cause, and if this can be solved by
> better solutions than making the threshold customizable. We can’t
> expect
> everyone to be able to pinpoint the culprit like you did :-)
>
> Yuan
Thanks! Let me know if I can help debugging :)
Best regards,
Ronan Arraes
next prev parent reply other threads:[~2022-12-21 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 14:08 bug#60223: 29.0.60; Improve how tree-sitter changes to treesit--font-lock-fast-mode ronisbr via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-21 4:17 ` Yuan Fu
2022-12-21 15:59 ` ronisbr via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-12-24 9:33 ` Yuan Fu
2022-12-27 3:16 ` ronisbr 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=d993fbc8e539624088eb9b3c4ce8abe8@ronanarraes.com \
--to=bug-gnu-emacs@gnu.org \
--cc=60223@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=ronisbr@ronanarraes.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 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).