From: Jimmy Wong <wyuenho@gmail.com>
To: Yuan Fu <casouri@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: 63755@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 [thread overview]
Message-ID: <d5a49f91-c218-4201-ab88-ede170ea51be@Spark> (raw)
In-Reply-To: <83zg5pit62.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
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@gnu.org>, wrote:
> > From: Jimmy Yuen Ho Wong <wyuenho@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?
[-- Attachment #2: Type: text/html, Size: 1578 bytes --]
prev parent reply other threads:[~2023-05-27 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 15:31 bug#63755: 29.0.91; json-ts-mode tree-sitter query error with tree-sitter 0.19 Jimmy Yuen Ho Wong
2023-05-27 17:24 ` Eli Zaretskii
2023-05-27 17:31 ` Jimmy Wong [this message]
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=d5a49f91-c218-4201-ab88-ede170ea51be@Spark \
--to=wyuenho@gmail.com \
--cc=63755@debbugs.gnu.org \
--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 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).