-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Failed to source nvim-treesitter.lua #29453
Comments
Make sure all your plugins are fully updated; also clean the |
@clason I'm not sure how to do either of those things. Running the command here https://vi.stackexchange.com/questions/43972/lazy-nvim-upgrade-plugins-from-command-line And there is no cache as mentioned here folke/lazy.nvim#29 |
Delete `vim.fn.stdpath('cache')..'/luac'. For the lazy.nvim questions, please use that plugin's support channels. |
Sorry to be dense, but I don't think that is the problem... Clearing the cache didn't work, and the problem isn't that the extensions aren't up to date, it's that it's trying to clone a repo that doesn't seem to exist anymore. |
Well, that's an issue with your config, isn't it? Try starting with a clean installation and adding things you know work one by one. This will tell you exactly where the problem comes from (or, more often, solve it). |
Ah—I have been enlightened. Had to go through these steps
No more problems. Thanks for putting up with me. |
Problem
I recently upgraded neovim using
brew upgrade neovim
and now whenever Invim
into any file, I get the below.Then, pressing any key, I get:
Which looks to be the case because the repo no longer exists.
Steps to reproduce
nvim
ing into any file produces thisExpected behavior
Normally it would just open the file without any problems, but I get the above error messages before I can access the file.
Neovim version (nvim -v)
v0.10.0
Vim (not Nvim) behaves the same?
vim works fine
Operating system/version
14.5
Terminal name/version
iTerm
$TERM environment variable
xterm-256color
Installation
brew install neovim
The text was updated successfully, but these errors were encountered: