中文

Now, I have two branches for neovim, one is using embed lsp, anothor is using coc.nvim.

Embed lsp is for geek customization, coc is for lightweight configuration.

In fact, I don’t want you to directly copy or git it down and use my configuration. My configuration is more suitable for myself. The role of my configuration is more often to provide you with an idea for your own configuration, so that you can Understand which plug-ins are needed, how to deal with dependencies, how to deal with file organization structure, and more!

For embed lsp users:

neovim version: 0.10

# for unix-like
git clone -b hybrid https://github.com/jinzhongjia/neovim-config.git ~/.config/nvim
# for windows
git clone -b hybrid https://github.com/jinzhongjia/neovim-config.git ~/AppData/Local/nvim

For coc users:

neovim version: latest release

# for unix-like
git clone -b coc https://github.com/jinzhongjia/neovim-config.git ~/.config/nvim
# for windows
git clone -b coc https://github.com/jinzhongjia/neovim-config.git ~/AppData/Local/nvim

• wget
• curl
• Golang
• Rust
• Python
• Nodejs
• Zig
• Gcc/Clang
• Lazygit
• Lazydocker
• fd (embed lsp)
• ripgrep (embed lsp)
• unzip (embed lsp)
• Cmake (embed lsp)
• Microsoft C++ Build Tools (For embed lsp and windows)

For GUI, you can install Neovide (My configuration includes neovide's configuration), this is a great GUI client!

When you install this configuration compeletely, you need to run:checkhealth for check whether has problem.

lsp server and guard denpendences are all installed by mason, you can use :mason to check installing information

coc depends nodejs, you may need to read coc help!