Skip to content
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

Closed
hopezh opened this issue Dec 2, 2023 · 11 comments
Closed

failed to update LuaSnip via Lazy.nvim #1071

hopezh opened this issue Dec 2, 2023 · 11 comments

Comments

@hopezh
Copy link

hopezh commented Dec 2, 2023

I got the following error and failed to update LuaSnip inside my LazyVim config.

May I ask if what it means, and how to fix this issue?

Thanks.

  Failed (1)
    ● LuaSnip 29.68ms 󰢱 luasnip  nvim-cmp
        You have local changes in `/Users/minioat/.local/share/OatLazyVim/lazy/LuaSnip`:
          * .github/workflows/luarocks.yml
          * .gitignore
          * .gitmodules
          * Makefile
          * deps/jsregexp
        Please remove them to update.
        You can also press `x` to remove the plugin and then `I` to install it again.

Screen image:
Screenshot 2023-12-02 at 11 31 49

@zer09
Copy link

zer09 commented Dec 2, 2023

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 LuaSnip

@hopezh
Copy link
Author

hopezh commented Dec 2, 2023

Yes, it works. Thank you very much.

@hopezh hopezh closed this as completed Dec 2, 2023
@L3MON4D3
Copy link
Owner

L3MON4D3 commented Dec 2, 2023

Aw man, I thought I'd sorted all of those out.
The latest commit updates the git-submodule that contains jstegexp, seems like something went wrong there.

I'm pretty sure applying the commit worked fine when I tried it on my end, seems like something is different..

@L3MON4D3
Copy link
Owner

L3MON4D3 commented Dec 2, 2023

I tried it again, worked fine despite some untracked files in the submodule :/
Not sure what is causing this for you guys, but I'll pin this issue, hopefully not too many others encounter this as well.

@rbjorklin
Copy link

Adding a "me too" and noting that I had to run rm -rf ~/.local/share/nvim/lazy/LuaSnip to get rid of the errors.

@seevee
Copy link

seevee commented Dec 4, 2023

I had this same issue today, seem to have resolved it by uninstalling and reinstalling LuaSnip from within the Lazy UI (x + i), as per comments on #1068

Possibly related, I do have the following in my .gitconfig:

[submodule]
  recurse = true

hisamafahri added a commit to hisamafahri/dotfiles that referenced this issue Dec 7, 2023
@gabeio
Copy link

gabeio commented Dec 7, 2023

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 jsregexp005) but I'm not well versed on submodules so I was unsuccessful and ended up moving it out of the way and forcing Lazy to reinstall it (which worked fine 🎉).

@iryan2
Copy link

iryan2 commented Dec 20, 2023

Just noting that I hit this too, and was able to resolve it thanks to the comments in this thread. All I did was rm -rf ~/.local/share/nvim/lazy/LuaSnip and Lazy correctly did it's thing the next time I opened vim. FWIW I don't have recurse in my .gitconfig.

kkafar added a commit to kkafar/neovim-config that referenced this issue Jan 4, 2024
kkafar added a commit to kkafar/neovim-config that referenced this issue Jan 4, 2024
@octocron
Copy link

Currently haf this issue today. I have placed the 3 lines correctly for Lazy using the plugin. Worked fine for a while...

Followed rm -rf ~/.local/share/nvim/lazy/LuaSnip reopened and it is working again.
Just wanted you to know this problem, whatever it is, still occurs.

@nicoandmee
Copy link

Currently haf this issue today. I have placed the 3 lines correctly for Lazy using the plugin. Worked fine for a while...

Followed rm -rf ~/.local/share/nvim/lazy/LuaSnip reopened and it is working again. Just wanted you to know this problem, whatever it is, still occurs.

Ditto. This fixed it for me.

@0x14Rp
Copy link

0x14Rp commented Apr 7, 2024

Currently haf this issue today. I have placed the 3 lines correctly for Lazy using the plugin. Worked fine for a while...

Followed rm -rf ~/.local/share/nvim/lazy/LuaSnip reopened and it is working again. Just wanted you to know this problem, whatever it is, still occurs.

this work for me! thx ^^

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants