-
Notifications
You must be signed in to change notification settings - Fork 944
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
Treesitter build failures on Windows #2
Comments
Hi! fyi: I've only started working on this config yesterday, so defintely not ready for real usage. I didnt have the time yet to test everything on Windows, and there's a bunch of things I still need to do. Closing this for now. I'll announce it on Reddit once this is ready. |
Can this be reopened? Found this through Reddit and am running into similar issues.
A second thing is treesitter Parsers not getting compiled correctly. I have a feeling this is related to the Troubleshooting portion here: https://github.com/nvim-treesitter/nvim-treesitter/wiki/Windows-support :checkhealth nvim-treesitter reports:
I'm running nvim 0.8.0 on Windows 11. MSys2 and LLVM are installed. |
This is definitely still an issue, Windows 11, LLVM and gcc installed. |
I'll look at it later today. Sorry for the delay! |
I just did a clean install on windows and for me all treesitter parsers install without an issue. |
When you close neovim and then open it back up, Treesitter doesn't try to install them all again? We are seeing this behavior on two different dev boxes (both installs exhibited the same issues reports in this ticket). We see :checkhealth reporting that all of the parsers are installed with no issues, but then when you close neovim and open it, the treesitter installs kick in again. (for context, this all works perfectly in WSL) |
I found the issue. LazyVim installed the latest release of nvim-treesitter, but unfortunately that release is pretty old and has issues. The issue you are encountering is nvim-treesitter/nvim-treesitter#2844 Luckily this has been fixed in the meantime, so I set To fix it, please update lazyvim and nvim-treesitter, restart Neovim and then run If that would fail again with an access denied error, then you'll need to delete the existing parsers at |
@folke That seems to have did the trick! Thank you so much! |
…ld and broken on Windows. Fixes LazyVim#2
I'm new to Vim/NeoVim and wish I knew better how to debug this. I've been trying configs (ThePrimeagen/init.lua, LunarVim/nvim-basic-ide, nvim-lua/kickstart.nvim) and rewriting a few dozen trying to learn before evolving in this direction. I didn't have any trouble getting the others up with TreeSitter & LSP functional but this one fails on Windows. Likely pathing issue? Target and Source seem to exist but getting access errors.
The text was updated successfully, but these errors were encountered: