.github | ||
lua | ||
.gitignore | ||
.stylua.toml | ||
init.lua | ||
LICENSE.md | ||
README.md |
nvim-config
Introduction
This is a fork of dam9000/kickstart-modular.nvim that represents my personal configuration of Neovim.
Installation
Install Neovim
Kickstart.nvim targets only the latest 'stable' and latest 'nightly' of Neovim. If you are experiencing issues, please make sure you have the latest versions.
Install External Dependencies
Note
Backup your previous configuration (if any exists)
External Requirements:
- Basic utils:
git
,make
,unzip
, C Compiler (gcc
) - ripgrep
- Language Setup:
- If want to write Typescript, you need
npm
- If want to write Golang, you will need
go
- etc.
- If want to write Typescript, you need
Note
See Windows Installation to double check any additional Windows notes
Neovim's configurations are located under the following paths, depending on your OS:
OS | PATH |
---|---|
Linux, MacOS | $XDG_CONFIG_HOME/nvim , ~/.config/nvim |
Windows (cmd) | %userprofile%\AppData\Local\nvim\ |
Windows (powershell) | $env:USERPROFILE\AppData\Local\nvim\ |
Install this Configuration
Clone it from GitHub:
Linux and Mac
git clone https://github.com/dam9000/kickstart-modular.nvim.git "${XDG_CONFIG_HOME:-$HOME/.config}"/nvim
Windows
If you're using cmd.exe
:
git clone https://github.com/Baipyrus/nvim-config.git %userprofile%\AppData\Local\nvim\
If you're using powershell.exe
git clone https://github.com/Baipyrus/nvim-config.git $env:USERPROFILE\AppData\Local\nvim\
Post Installation
Start Neovim
nvim
That's it! Lazy will install all the plugins you have. Use :Lazy
to view
current plugin status.
FAQ
- What should I do if I already have a pre-existing neovim configuration?
- You should back it up, then delete all files associated with it.
- This includes your existing init.lua and the neovim files in
~/.local
which can be deleted withrm -rf ~/.local/share/nvim/
or their windows counterparts inAppData\Local\nvim-data
- Can I keep my existing configuration in parallel to kickstart?
- Yes! You can use NVIM_APPNAME
=nvim-NAME
to maintain multiple configurations. For example you can install the kickstart configuration in~/.config/nvim-kickstart
and create an alias:
When you run Neovim usingalias nvim-kickstart='NVIM_APPNAME="nvim-kickstart" nvim'
nvim-kickstart
alias it will use the alternative config directory and the matching local directory~/.local/share/nvim-kickstart
. You could also run your configuration inline, for example in Windows Powershell:$env:NVIM_APPNAME = 'nvim-kickstart'; nvim
- Yes! You can use NVIM_APPNAME
- What if I want to "uninstall" this configuration:
- See lazy.nvim uninstall information
Windows Installation
Installation requires gcc and make, for which you don't need to change the config, the easiest way is to use choco:
- install chocolatey either follow the instructions on the page or use winget, run in cmd as admin:
winget install --accept-source-agreements chocolatey.chocolatey
- 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
Then continue with the Install Kickstart step.