2024-03-06 06:55:22 +00:00
# nvim-config
2024-01-10 12:28:46 +00:00
## Introduction
2023-02-17 21:31:57 +00:00
2024-03-06 06:55:22 +00:00
*This is a fork of [dam9000/kickstart-modular.nvim ](https://github.com/dam9000/kickstart-modular.nvim ) that represents my personal configuration of Neovim.*
## Installation
2023-07-01 15:21:10 +00:00
2024-03-06 06:55:22 +00:00
### Install Neovim
2022-06-24 03:35:53 +00:00
2024-03-06 06:55:22 +00:00
Kickstart.nvim targets *only* the latest
['stable' ](https://github.com/neovim/neovim/releases/tag/stable ) and latest
['nightly' ](https://github.com/neovim/neovim/releases/tag/nightly ) of Neovim.
If you are experiencing issues, please make sure you have the latest versions.
### Install External Dependencies
2022-06-24 03:35:53 +00:00
2024-01-10 12:28:46 +00:00
> **NOTE**
2023-09-05 12:12:56 +00:00
> [Backup](#FAQ) your previous configuration (if any exists)
2024-03-06 06:55:22 +00:00
External Requirements:
- Basic utils: `git` , `make` , `unzip` , C Compiler (`gcc`)
- [ripgrep ](https://github.com/BurntSushi/ripgrep#installation )
2024-03-08 23:24:54 +00:00
- A [Nerd Font ](https://www.nerdfonts.com/ ): provides various icons
- Language utils: `rustup` , `npm` , `dotnet` , `python`
- Optionally, install [Alacritty ](https://github.com/alacritty/alacritty#installation )
- Or on Windows, just install using `winget install alacritty --source winget`
2024-03-06 06:55:22 +00:00
> **NOTE**
2024-03-17 20:22:58 +00:00
> See [Install Recipes](#Install-Recipes) for additional Windows and Linux specific notes
> and quick install snippets
2024-03-06 06:55:22 +00:00
Neovim's configurations are located under the following paths, depending on your OS:
2023-09-05 12:12:56 +00:00
2024-03-06 06:55:22 +00:00
| OS | PATH |
2023-09-05 12:12:56 +00:00
| :- | :--- |
2024-03-06 06:55:22 +00:00
| Linux, MacOS | `$XDG_CONFIG_HOME/nvim` , `~/.config/nvim` |
| Windows (cmd)| `%userprofile%\AppData\Local\nvim\` |
| Windows (powershell)| `$env:USERPROFILE\AppData\Local\nvim\` |
2023-11-03 12:47:30 +00:00
2024-03-06 06:55:22 +00:00
### Install this Configuration
2023-11-03 12:47:30 +00:00
2024-03-06 06:55:22 +00:00
Clone it from GitHub:
2023-09-05 12:12:56 +00:00
2024-03-06 06:55:22 +00:00
< details > < summary > Linux and Mac < / summary >
2023-10-25 19:46:24 +00:00
```sh
2024-03-08 23:25:14 +00:00
git clone https://github.com/Baipyrus/nvim-config.git "${XDG_CONFIG_HOME:-$HOME/.config}"/nvim
2023-10-25 19:46:24 +00:00
```
2024-03-06 06:55:22 +00:00
< / details >
< details > < summary > Windows < / summary >
2023-10-25 19:46:24 +00:00
2024-03-06 06:55:22 +00:00
If you're using `cmd.exe` :
```bat
git clone https://github.com/Baipyrus/nvim-config.git %userprofile%\AppData\Local\nvim\
```
If you're using `powershell.exe`
```pwsh
git clone https://github.com/Baipyrus/nvim-config.git $env:USERPROFILE\AppData\Local\nvim\
```
< / details >
### Post Installation
2024-03-08 23:25:43 +00:00
< details > < summary > Extras for Linux and Mac < / summary >
In the [`options` ](./lua/options.lua ) file, change the settings to specify the terminal of your choice. This installation is used and maintained by a Windows user and, as such, will use Powershell. This setting may need to be updated after each upgrade.
< / details >
2024-03-06 06:55:22 +00:00
Start Neovim
2023-09-05 12:12:56 +00:00
```sh
2024-03-06 06:55:22 +00:00
nvim
2023-09-05 12:12:56 +00:00
```
2024-03-06 06:55:22 +00:00
That's it! Lazy will install all the plugins you have. Use `:Lazy` to view
current plugin status.
2022-12-20 18:27:01 +00:00
### FAQ
2023-02-17 21:31:57 +00:00
* What should I do if I already have a pre-existing neovim configuration?
2024-03-08 20:26:32 +00:00
* You should back it up and then delete all associated files.
2024-03-21 19:47:55 +00:00
* This includes your existing init.lua and the neovim files in `~/.local`
2024-03-27 10:18:17 +00:00
which can be deleted with `rm -rf ~/.local/share/nvim/` or their
windows counterparts in `AppData\Local\nvim-data`
2024-03-06 06:55:22 +00:00
* Can I keep my existing configuration in parallel to kickstart?
2024-03-21 19:47:55 +00:00
* Yes! You can use [NVIM_APPNAME ](https://neovim.io/doc/user/starting.html#%24NVIM_APPNAME )`=nvim-NAME`
to maintain multiple configurations. For example, you can install the kickstart
configuration in `~/.config/nvim-kickstart` and create an alias:
2024-03-06 06:55:22 +00:00
```sh
alias nvim-kickstart='NVIM_APPNAME="nvim-kickstart" nvim'
```
2024-03-21 19:47:55 +00:00
When you run Neovim using `nvim-kickstart` alias it will use the alternative
2024-03-27 10:18:17 +00:00
config directory and the matching local directory `~/.local/share/nvim-kickstart` .
2024-03-06 06:55:22 +00:00
You could also run your configuration inline, for example in Windows Powershell:
```pwsh
$env:NVIM_APPNAME = 'nvim-kickstart'; nvim
```
2023-02-17 21:31:57 +00:00
* What if I want to "uninstall" this configuration:
* See [lazy.nvim uninstall ](https://github.com/folke/lazy.nvim#-uninstalling ) information
2024-03-17 20:22:58 +00:00
### Install Recipes
2024-03-06 06:55:22 +00:00
2024-03-17 20:22:58 +00:00
Below you can find OS specific install instructions for Neovim and dependencies.
After installing all the dependencies continue with the [Install Kickstart ](#Install-Kickstart ) step.
#### Windows Installation
< details > < summary > Windows with Microsoft C++ Build Tools and CMake< / summary >
2024-03-08 20:26:32 +00:00
Installation may require installing build tools and updating the run command for `telescope-fzf-native`
2023-02-17 21:31:57 +00:00
2023-04-13 13:34:27 +00:00
See `telescope-fzf-native` documentation for [more details ](https://github.com/nvim-telescope/telescope-fzf-native.nvim#installation )
2023-02-17 21:31:57 +00:00
This requires:
2024-03-08 20:26:32 +00:00
- Install CMake and the Microsoft C++ Build Tools on Windows
2023-02-17 21:31:57 +00:00
2024-03-27 10:18:17 +00:00
Using this, you can change some plugin configurations such as `telescope-fzf-native` to use `cmake` :
2023-02-17 21:31:57 +00:00
```lua
2023-02-19 20:32:15 +00:00
{'nvim-telescope/telescope-fzf-native.nvim', build = 'cmake -S. -Bbuild -DCMAKE_BUILD_TYPE=Release & & cmake --build build --config Release & & cmake --install build --prefix build' }
2023-02-17 21:31:57 +00:00
```
2024-03-17 20:22:58 +00:00
< / details >
< details > < summary > Windows with gcc/make using chocolatey< / summary >
2024-03-08 20:26:32 +00:00
Alternatively, one can install gcc and make which don't require changing the config,
2024-03-06 06:55:22 +00:00
the easiest way is to use choco:
1. install [chocolatey ](https://chocolatey.org/install )
either follow the instructions on the page or use winget,
run in cmd as **admin** :
```
winget install --accept-source-agreements chocolatey.chocolatey
```
2. install all requirements using choco, exit previous cmd and
2024-03-08 20:26:32 +00:00
open a new one so that choco path is set, and run in cmd as **admin** :
2024-03-06 06:55:22 +00:00
```
choco install -y neovim git ripgrep wget fd unzip gzip mingw make
```
2024-03-17 20:22:58 +00:00
< / details >
< details > < summary > WSL (Windows Subsystem for Linux)< / summary >
```
wsl --install
wsl
sudo add-apt-repository ppa:neovim-ppa/unstable -y
sudo apt update
sudo apt install make gcc ripgrep unzip neovim
```
< / details >
#### Linux Install
< details > < summary > Ubuntu Install Steps< / summary >
2024-03-06 06:55:22 +00:00
2024-03-17 20:22:58 +00:00
```
sudo add-apt-repository ppa:neovim-ppa/unstable -y
sudo apt update
sudo apt install make gcc ripgrep unzip neovim
```
< / details >
< details > < summary > Debian Install Steps< / summary >
```
sudo apt update
sudo apt install make gcc ripgrep unzip git
echo "deb https://deb.debian.org/debian unstable main" | sudo tee -a /etc/apt/sources.list
sudo apt update
sudo apt install -t unstable neovim
```
< / details >
< details > < summary > Fedora Install Steps< / summary >
```
sudo dnf install -y gcc make git ripgrep fd-find neovim
```
< / details >