GNU bug report logs - #63755
29.0.91; json-ts-mode tree-sitter query error with tree-sitter 0.19

Previous Next

Full log

View this message in rfc822 format

From: Jimmy Wong <wyuenho <at> gmail.com>
To: Yuan Fu <casouri <at> gmail.com>, Eli Zaretskii <eliz <at> gnu.org>
Cc: 63755 <at> debbugs.gnu.org
Subject: bug#63755: 29.0.91; json-ts-mode tree-sitter query error with tree-sitter 0.19
Date: Sat, 27 May 2023 18:31:24 +0100

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

Yes, it’s similar as #63086, I think it’s probably worth double checking all the *-ts-modes works with the latest released tree-sitter version. tree-sitter-json 0.19 does not allow comments or top level values.
On 27 May 2023 at 6:24 PM +0100, Eli Zaretskii <eliz <at> gnu.org>, wrote:
> > From: Jimmy Yuen Ho Wong <wyuenho <at> gmail.com>
> > Date: Sat, 27 May 2023 16:31:14 +0100
> >
> >
> > Reproduction:
> >
> > 1. echo '{ "hello" : 1 }' > test.json
> > 2. open /path/to/ns-port-emacs-29 ./test.json --args -q
> > 3. M-x json-ts-mode
> > 4. Observe font-lock is not working in the buffer and the following
> > message in the *Messages* buffer:
> >
> > ```
> > Error during redisplay: (jit-lock-function 1) signaled (treesit-query-error "Node type error at" 2 "(comment) @font-lock-comment-face" "Debug the query with `treesit-query-validate'")
> > ```
>
> I cannot reproduce this: the font-lock works fine for me, and I see no
> error messages in *Messages*.
>
> Maybe your JSON grammar is not the latest one or something?
>
> Yuan, could you please look into this?

[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.