From: Randy Taylor <dev@rjt.dev>
To: Jimmy Wong <wyuenho@gmail.com>
Cc: Yuan Fu <casouri@gmail.com>,
63086@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#63086: 29.0.90; go-ts-mode treesit-query-error during jit-lock
Date: Wed, 26 Apr 2023 12:38:34 +0000 [thread overview]
Message-ID: <i3WV_W9WIVoVcha9N7LQ8dt7eCfCGE4SdEoJT_2-rux9RIeoVj_GKNpehdGyDyeWB355UiKjE7Te5__FvouhONtUia96ahh5dHgQOtvW0qU=@rjt.dev> (raw)
In-Reply-To: <077666b3-657b-4b35-b271-78d6bd26d2df@Spark>
[-- Attachment #1: Type: text/plain, Size: 1555 bytes --]
On Wednesday, April 26th, 2023 at 07:07, Jimmy Wong <wyuenho@gmail.com> wrote:
> Any go file will trigger this
> On 26 Apr 2023 at 11:35 AM +0100, Eli Zaretskii <eliz@gnu.org>, wrote:
>
>>> From: Jimmy Yuen Ho Wong <wyuenho@gmail.com>
>>> Date: Wed, 26 Apr 2023 11:00:14 +0100
>>>
>>> After visiting a go file and turning on M-x go-ts-mode, this following
>>> message appears in the *Messages* buffer and the go buffer is not
>>> highlighted as a result.
>>>
>>> QuitError during redisplay: (jit-lock-function 1) signaled (treesit-query-error "Node type error at" 11 "[(false) (iota) (nil) (true)] @font-lock-constant-face (const_declaration (const_spec name: (identifier) @font-lock-constant-face))" "Debug the query with `treesit-query-validate'")
>>> Error during redisplay: (jit-lock-function 1) signaled (treesit-query-error "Node type error at" 11 "[(false) (iota) (nil) (true)] @font-lock-constant-face (const_declaration (const_spec name: (identifier) @font-lock-constant-face))" "Debug the query with `treesit-query-validate'")
>>
>> Can you post a minimal file that triggers this? Or are you saying
>> that any Go file will cause this?
>>
>> Thanks.
I can't reproduce this with any .go files I have laying around. Can you share one that reproduces the issue?
Is the tree-sitter-go shared library file you're using the latest and most up to date one?
What is the version of tree-sitter? If it's not the latest, can you try the latest and see if that helps?
Also, and just to be on the safe side, are you able to reproduce this with emacs -Q?
[-- Attachment #2: Type: text/html, Size: 2777 bytes --]
next prev parent reply other threads:[~2023-04-26 12:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 10:00 bug#63086: 29.0.90; go-ts-mode treesit-query-error during jit-lock Jimmy Yuen Ho Wong
2023-04-26 10:36 ` Eli Zaretskii
2023-04-26 11:07 ` Jimmy Wong
2023-04-26 12:38 ` Randy Taylor [this message]
2023-04-26 13:26 ` Jimmy Wong
2023-04-26 13:38 ` Eli Zaretskii
2023-04-26 13:44 ` Jimmy Wong
2023-04-26 14:05 ` Randy Taylor
2023-04-26 15:40 ` Randy Taylor
2023-04-27 6:36 ` Jimmy Wong
2023-04-28 0:16 ` Dmitry Gutov
2023-04-28 1:35 ` Randy Taylor
2023-04-28 10:05 ` Dmitry Gutov
2023-05-02 0:29 ` Randy Taylor
2023-05-03 21:58 ` Dmitry Gutov
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='i3WV_W9WIVoVcha9N7LQ8dt7eCfCGE4SdEoJT_2-rux9RIeoVj_GKNpehdGyDyeWB355UiKjE7Te5__FvouhONtUia96ahh5dHgQOtvW0qU=@rjt.dev' \
--to=dev@rjt.dev \
--cc=63086@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=eliz@gnu.org \
--cc=wyuenho@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 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).