-
Notifications
You must be signed in to change notification settings - Fork 23k
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
windows install instructions #662
Comments
Awesome! would it make sense to add fzf to your chocolatey invocation or is that taken care of elsewhere? |
telescope-fzf-native.nvim does not use the fzf tool which is written in go, instead it builds a fzf library which is implemented in C so it's faster. It does this at plugin install:
it's built using
|
As @feoh got me to test out windows nvim+kickstart in #654
I experimented what would be the easiest way to install all requirements to get kickstart fully working on windows, and here is what I came up with:
easiest is using winget, run in cmd as admin:
(exit previous cmd and open a new one so that choco path is set)
run in cmd as admin:
NOTE: in case winget is not already installed, you can get it here:
https://learn.microsoft.com/en-us/windows/package-manager/winget/
https://apps.microsoft.com/detail/9nblggh4nns1
or install chocolatey following the instruction: https://chocolatey.org/install
I tested this with a fresh windows 10 install (in virtualbox) and it works perfectly, it installs everything required so that the tressitter parsers and telescope-fzf-native get built, and it satisfies all the various :checkhealth requirements.
I would have preferred to use just winget for all packages but it does not provide all that are required hence using choco instead.
Should I open a PR to include these instructions in the README?
The text was updated successfully, but these errors were encountered: