-
Notifications
You must be signed in to change notification settings - Fork 328
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
bug: Lazy Fails to Detect Different Plugins If They Have The Same Repository Name #337
Comments
Duplicate of #331 |
Just added an error message when two specs have the same name and a differen url. It was already shown in To solve this, just use |
I think this is relevant here but if you want me to open up a separate issue I can do that too.. If you have a fork of a plugin, then switch from the main to the fork, Lazy doesn't correctly see that there are updates that exist. I discovered this as I am rewriting ionide-vim all in lua, because I'm a masochist, evidently. (actually it's an attempt to understand how any of this works, while hopefully making meaningful contribution to the fsharp community.. but.. also.. it hurts, coach... ) When I switch from pointing from ionide/ionide-vim to willehrendreich/ionide-vim, lazy doesn't see that it needs updates. The update checking claims it's perfectly fine. As a work around, I can of course delete the directory that stores it, but I thought it might be helpful to point it out to you that this happens. Thanks for all your awesome work, @folke, you make some great stuff. |
actually there is an issue for this somewhere |
#331, I referenced that issue in mine. |
@WillEhrendreich when the origin url changes, lazy does detect that. Doing a |
Did you check docs and existing issues?
Neovim version (nvim -v)
NVIM v0.8.2
Operating system/version
Windows 10 + WSL
Describe the bug
When two or more plugins with the same repository name are present, Lazy does not recognize all of them.
This issue is related to #331.
Steps To Reproduce
Expected Behavior
Lazy would identify that the plugins are different and handle them accordingly.
Repro
The text was updated successfully, but these errors were encountered: