-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Broken rust query #513
Comments
same, getting this after update |
This issue happens after |
I also ran into the same problem. You can avoid the error by commenting out keymaps.
commit hash |
If anyone is using Lazy for package management, just add the commit hash while adding the plugin and sync.
Mitigates the issue for now, until an upstream patch is available. |
Describe the bug
Hey!
I'm getting an error when opening rust files.
As far as I understand this tells me that some query is wrong. I tried to open queries for rust and saw that one of them is highlighted for some reason.
After commenting it out I don't see an error.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No error
Output of
:checkhealth nvim-treesitter
==============================================================================
nvim-treesitter: require("nvim-treesitter.health").check()
Installation ~
tree-sitter
found 0.20.7 (parser generator, only needed for :TSInstallFromGrammar)node
found v18.2.0 (only needed for :TSInstallFromGrammar)git
executable found.cc
executable found. Selected from { vim.NIL, "cc", "gcc", "clang", "cl", "zig" }Version: Apple clang version 15.0.0 (clang-1500.0.40.1)
OS Info:
{
machine = "arm64",
release = "22.6.0",
sysname = "Darwin",
version = "Darwin Kernel Version 22.6.0: Wed Jul 5 22:22:05 PDT 2023; root:xnu-8796.141.3~6/RELEASE_ARM64_T6000"
} ~
Parser/Features H L F I J
Legend: H[ighlight], L[ocals], F[olds], I[ndents], In[j]ections
+) multiple parsers found, only one will be used
x) errors found in the query, try to run :TSUpdate {lang} ~
Output of
nvim --version
Additional context
Didn't manage to fix this query myself, don't really understand what it does. But will contribute a fix if someone willing to help.
The text was updated successfully, but these errors were encountered: