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

Can't install lewis6991/gitsigns.nvim #44

Closed
cronyakatsuki opened this issue Jun 23, 2021 · 5 comments
Closed

Can't install lewis6991/gitsigns.nvim #44

cronyakatsuki opened this issue Jun 23, 2021 · 5 comments

Comments

@cronyakatsuki
Copy link

I have been trying to use paq since it works better on windows than packer, but haven't been able to install gitsigns, it say that it did but when I launch gitsings next time it shows me this error: Error executing luv callback: ...pack\paqs\start\plenary.nvim\lua\plenary\async\async.lua:14: The coroutine failed with this message: ...site\pack\paqs\start\gitsigns.nvim\lua\gitsigns\diff.lua:141: cannot resolve symbol 'xdl_diff': The specified procedure could not be found.

@cronyakatsuki
Copy link
Author

Just checked and it does install with packer.nvim, but it is in a wsl enviroments so I suspect that it is a paq error.

@savq
Copy link
Owner

savq commented Jun 23, 2021

I'm not sure I understand. Were you trying to install gitsigns.nvim with Paq in Windows, and then with Packer in WSL? Or were you using both in WSL?

@cronyakatsuki
Copy link
Author

I used both paq and packer in windows(packer doesn't work at all in windows and paq only doesn't install gitsigns) and both paq and packer in wsl (packer works perfectly and installs all, while paq doesn't install gitsings even in wsl).

@savq
Copy link
Owner

savq commented Jun 28, 2021

From the error message it looks like gitsigns does install. It shows the path where it's installed and all.

Looking at the docs it says there are features that are not enabled in Windows. See :help gitsigns-config-use_internal_diff

So it seems gitsigns installs, but then fails to load, in which case that would be a problem with the plugin, not the package manager.

See also: lewis6991/gitsigns.nvim#90

@cronyakatsuki
Copy link
Author

Ok then, thank you very much for checking the issue.

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

2 participants