GNU bug report logs - #63086
29.0.90; go-ts-mode treesit-query-error during jit-lock

Previous Next

Full log

View this message in rfc822 format

From: Jimmy Wong <wyuenho <at> gmail.com>
To: Randy Taylor <dev <at> rjt.dev>, Yuan Fu <casouri <at> gmail.com>, Eli Zaretskii <eliz <at> gnu.org>
Cc: 63086 <at> debbugs.gnu.org
Subject: bug#63086: 29.0.90; go-ts-mode treesit-query-error during jit-lock
Date: Wed, 26 Apr 2023 12:07:53 +0100

[Message part 1 (text/plain, inline)]

Any go file will trigger this
On 26 Apr 2023 at 11:35 AM +0100, Eli Zaretskii <eliz <at> gnu.org>, wrote:
> > From: Jimmy Yuen Ho Wong <wyuenho <at> 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.

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.