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

windows install instructions #662

Closed
dam9000 opened this issue Feb 29, 2024 · 2 comments · Fixed by #674
Closed

windows install instructions #662

dam9000 opened this issue Feb 29, 2024 · 2 comments · Fixed by #674

Comments

@dam9000
Copy link
Contributor

dam9000 commented Feb 29, 2024

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:

  1. install chocolatey https://chocolatey.org/
    easiest is using winget, run in cmd as admin:
winget install --accept-source-agreements chocolatey.chocolatey
  1. install all requirements using choco:
    (exit previous cmd and open a new one so that choco path is set)
    run in cmd as admin:
choco install -y neovim git ripgrep wget fd unzip gzip mingw make
  1. run in cmd as user
git clone https://github.com/nvim-lua/kickstart.nvim.git %userprofile%\AppData\Local\nvim\

nvim

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?

@feoh
Copy link
Collaborator

feoh commented Feb 29, 2024

Awesome! would it make sense to add fzf to your chocolatey invocation or is that taken care of elsewhere?

@dam9000
Copy link
Contributor Author

dam9000 commented Feb 29, 2024

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:

      { -- If encountering errors, see telescope-fzf-native README for install instructions
        'nvim-telescope/telescope-fzf-native.nvim',

        -- `build` is used to run some command when the plugin is installed/updated.
        -- This is only run then, not every time Neovim starts up.
        build = 'make',

        -- `cond` is a condition used to determine whether this plugin should be
        -- installed and loaded.
        cond = function()
          return vim.fn.executable 'make' == 1
        end,
      },

it's built using make and expects a working c compiler.
The library gets then installed to:

linux:
.local/share/nvim/lazy/telescope-fzf-native.nvim/build/libfzf.so
windows:
C:\Users\USER\AppData\Local\nvim-data\lazy\telescope-fzf-native.nvim\build\libfzf.dll

:checkhealth reports that telescope-fzf is ok:

Telescope Extension: `fzf` ~
- OK lib working as expected
- OK file_sorter correctly configured
- OK generic_sorter correctly configured

dam9000 added a commit to dam9000/kickstart-modular.nvim that referenced this issue Mar 2, 2024
@feoh feoh closed this as completed in #674 Mar 3, 2024
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

Successfully merging a pull request may close this issue.

2 participants