-
-
Notifications
You must be signed in to change notification settings - Fork 247
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 update LuaSnip
via Lazy.nvim
#1071
Comments
add this {
"L3MON4D3/LuaSnip",
-- follow latest release.
version = "v2.*", -- Replace <CurrentMajor> by the latest released major (first number of latest release)
-- install jsregexp (optional!).
build = "make install_jsregexp"
} then reinstall |
Yes, it works. Thank you very much. |
Aw man, I thought I'd sorted all of those out. I'm pretty sure applying the commit worked fine when I tried it on my end, seems like something is different.. |
I tried it again, worked fine despite some untracked files in the submodule :/ |
Adding a "me too" and noting that I had to run |
I had this same issue today, seem to have resolved it by uninstalling and reinstalling LuaSnip from within the Lazy UI ( Possibly related, I do have the following in my [submodule]
recurse = true |
I was running a pretty old version (v.2.1.1) when I tried to upgrade and hit this issue (this might be useful info?). I tried a few things like trying to reclone/checkout the submodule (specifically |
Just noting that I hit this too, and was able to resolve it thanks to the comments in this thread. All I did was |
Fix luasnip configuration (see details) L3MON4D3/LuaSnip#1071
Currently haf this issue today. I have placed the 3 lines correctly for Lazy using the plugin. Worked fine for a while... Followed |
Ditto. This fixed it for me. |
this work for me! thx ^^ |
I got the following error and failed to update
LuaSnip
inside myLazyVim
config.May I ask if what it means, and how to fix this issue?
Thanks.
Screen image:

The text was updated successfully, but these errors were encountered: