From: Randy Taylor <dev@rjt.dev>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: casouri@gmail.com, Eli Zaretskii <eliz@gnu.org>,
63086@debbugs.gnu.org, Jimmy Wong <wyuenho@gmail.com>
Subject: bug#63086: 29.0.90; go-ts-mode treesit-query-error during jit-lock
Date: Fri, 28 Apr 2023 01:35:13 +0000 [thread overview]
Message-ID: <sVaonIb2lJW_pzqyzMFotzskDTn4CzwC1xedRlRJfij5nRGpUTAKBHfQPWGATyHuETa4CTfFPOsyEbA7JgGlB4ZmKe_GvxCmmX2t1-ryMMI=@rjt.dev> (raw)
In-Reply-To: <9dfa3e61-87b9-04cf-21e6-6049ee3fed41@gutov.dev>
On Thursday, April 27th, 2023 at 20:16, Dmitry Gutov <dmitry@gutov.dev> wrote:
>
> On 26/04/2023 17:05, Randy Taylor wrote:
>
> > I think java-ts-mode and some others have a helper that checks which
> > queries are supported by testing them, I can make a patch for that if
> > that's the direction we want to go.
>
>
> It might be better to use treesit-query-string instead, see
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=61913#55.
Thanks.
Maybe I'm missing something, but doesn't treesit-query-string with an empty string do nothing and always error, since it queries on whatever string you pass in?
In that case, wouldn't using treesit-query-capture directly be the best? I don't understand why it's not from reading that thread. If it isn't, then treesit-query-validate is the only option, right?
next prev parent reply other threads:[~2023-04-28 1:35 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
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 [this message]
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='sVaonIb2lJW_pzqyzMFotzskDTn4CzwC1xedRlRJfij5nRGpUTAKBHfQPWGATyHuETa4CTfFPOsyEbA7JgGlB4ZmKe_GvxCmmX2t1-ryMMI=@rjt.dev' \
--to=dev@rjt.dev \
--cc=63086@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=dmitry@gutov.dev \
--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).