2023-02-17 21:31:57 +00:00
# kickstart.nvim
2024-02-26 15:03:53 +00:00
## Introduction
2022-06-24 03:35:53 +00:00
2022-11-09 15:27:08 +00:00
A starting point for Neovim that is:
2022-06-24 03:35:53 +00:00
2023-02-17 21:31:57 +00:00
* Small
2024-02-26 15:03:53 +00:00
* Single-file
* Completely Documented
**NOT** a Neovim distribution, but instead a starting point for your configuration.
2022-06-24 03:35:53 +00:00
2024-02-26 15:03:53 +00:00
## Installation
2022-06-24 03:35:53 +00:00
2024-02-26 15:03:53 +00:00
### Install Neovim
2023-04-24 21:21:53 +00:00
2024-02-26 15:03:53 +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.
2022-06-24 03:35:53 +00:00
2024-02-26 15:03:53 +00:00
### Install External Dependencies
2022-11-09 15:27:08 +00:00
2024-03-04 13:47:11 +00:00
> **NOTE**
2023-09-05 12:12:56 +00:00
> [Backup](#FAQ) your previous configuration (if any exists)
2024-02-26 15:03:53 +00:00
External Requirements:
- Basic utils: `git` , `make` , `unzip` , C Compiler (`gcc`)
- [ripgrep ](https://github.com/BurntSushi/ripgrep#installation )
- Language Setup:
- If want to write Typescript, you need `npm`
- If want to write Golang, you will need `go`
- etc.
> **NOTE**
> See [Windows Installation](#Windows-Installation) to double check any additional Windows notes
2023-09-05 12:12:56 +00:00
Neovim's configurations are located under the following paths, depending on your OS:
| OS | PATH |
| :- | :--- |
2024-02-26 15:03:53 +00:00
| Linux, MacOS | `$XDG_CONFIG_HOME/nvim` , `~/.config/nvim` |
2023-11-03 12:47:30 +00:00
| Windows (cmd)| `%userprofile%\AppData\Local\nvim\` |
| Windows (powershell)| `$env:USERPROFILE\AppData\Local\nvim\` |
2023-09-05 12:12:56 +00:00
2024-03-03 02:12:55 +00:00
### Install Kickstart
2023-09-07 16:36:05 +00:00
Clone kickstart.nvim:
2023-09-05 12:12:56 +00:00
2024-02-26 15:03:53 +00:00
< details > < summary > Linux and Mac < / summary >
2023-11-30 00:34:43 +00:00
```sh
2023-09-07 16:36:05 +00:00
git clone https://github.com/nvim-lua/kickstart.nvim.git "${XDG_CONFIG_HOME:-$HOME/.config}"/nvim
2023-10-01 00:06:22 +00:00
```
2024-02-26 15:03:53 +00:00
< / details >
< details > < summary > Windows < / summary >
If you're using `cmd.exe` :
2023-11-30 00:34:43 +00:00
```
2024-03-04 13:47:11 +00:00
git clone https://github.com/nvim-lua/kickstart.nvim.git %userprofile%\AppData\Local\nvim\
2023-09-05 12:12:56 +00:00
```
2024-02-26 15:03:53 +00:00
If you're using `powershell.exe`
2023-11-30 00:34:43 +00:00
```
2024-03-04 13:47:11 +00:00
git clone https://github.com/nvim-lua/kickstart.nvim.git $env:USERPROFILE\AppData\Local\nvim\
2023-11-03 12:47:30 +00:00
```
2024-02-26 15:03:53 +00:00
< / details >
2023-11-03 12:47:30 +00:00
2023-09-05 12:12:56 +00:00
### Post Installation
2023-10-25 19:46:24 +00:00
Start Neovim
```sh
nvim
```
2024-02-26 15:03:53 +00:00
That's it! Lazy will install all the plugins you have. Use `:Lazy` to view
current plugin status.
2023-10-25 19:46:24 +00:00
2024-02-26 15:03:53 +00:00
Read through the `init.lua` file in your configuration folder for more
information about extending and exploring Neovim.
2023-09-05 12:12:56 +00:00
2024-01-08 19:44:00 +00:00
### Getting Started
2024-01-03 15:03:23 +00:00
2024-03-04 13:47:45 +00:00
[The Only Video You Need to Get Started with Neovim ](https://youtu.be/m8C0Cq9Uv9o )
2024-01-03 15:03:23 +00:00
2023-09-07 16:36:05 +00:00
### Recommended Steps
2023-09-05 12:12:56 +00:00
2024-02-26 15:03:53 +00:00
[Fork ](https://docs.github.com/en/get-started/quickstart/fork-a-repo ) this repo
(so that you have your own copy that you can modify) and then installing you
can install to your machine using the methods above.
2023-09-05 12:12:56 +00:00
2024-03-04 13:47:11 +00:00
> **NOTE**
2023-09-05 12:12:56 +00:00
> Your fork's url will be something like this: `https://github.com/<your_github_username>/kickstart.nvim.git`
2022-12-20 18:27:01 +00:00
2024-02-26 15:03:53 +00:00
#### Examples of adding popularly requested plugins
2022-12-22 12:45:20 +00:00
2024-03-03 08:13:16 +00:00
NOTE: You'll need to uncomment the line in the init.lua that turns on loading custom plugins.
2024-02-26 15:03:53 +00:00
< details >
< summary > Adding autopairs< / summary >
2022-12-22 12:45:20 +00:00
2024-02-26 15:03:53 +00:00
This will automatically install [windwp/nvim-autopairs ](https://github.com/windwp/nvim-autopairs ) and enable it on startup. For more information, see documentation for [lazy.nvim ](https://github.com/folke/lazy.nvim ).
2022-12-22 12:45:20 +00:00
2023-02-17 21:31:57 +00:00
In the file: `lua/custom/plugins/autopairs.lua` , add:
2022-12-22 12:45:20 +00:00
```lua
2023-02-17 21:31:57 +00:00
-- File: lua/custom/plugins/autopairs.lua
return {
"windwp/nvim-autopairs",
2023-05-22 18:29:42 +00:00
-- Optional dependency
dependencies = { 'hrsh7th/nvim-cmp' },
2023-02-17 21:31:57 +00:00
config = function()
require("nvim-autopairs").setup {}
2023-05-22 18:29:42 +00:00
-- If you want to automatically add `(` after selecting a function or method
local cmp_autopairs = require('nvim-autopairs.completion.cmp')
local cmp = require('cmp')
cmp.event:on(
'confirm_done',
cmp_autopairs.on_confirm_done()
)
2023-02-17 21:31:57 +00:00
end,
}
2022-12-22 12:45:20 +00:00
```
2024-02-26 15:03:53 +00:00
< / details >
< details >
< summary > Adding a file tree plugin< / summary >
2022-11-21 12:47:24 +00:00
2024-02-26 15:03:53 +00:00
This will install the tree plugin and add the command `:Neotree` for you. You can explore the documentation at [neo-tree.nvim ](https://github.com/nvim-neo-tree/neo-tree.nvim ) for more information.
2022-11-21 12:47:24 +00:00
2023-02-17 21:31:57 +00:00
In the file: `lua/custom/plugins/filetree.lua` , add:
2022-11-21 12:47:24 +00:00
```lua
2023-02-27 21:36:59 +00:00
-- Unless you are still migrating, remove the deprecated commands from v1.x
vim.cmd([[ let g:neo_tree_remove_legacy_commands = 1 ]])
2023-02-17 21:31:57 +00:00
return {
"nvim-neo-tree/neo-tree.nvim",
version = "*",
dependencies = {
"nvim-lua/plenary.nvim",
"nvim-tree/nvim-web-devicons", -- not strictly required, but recommended
"MunifTanjim/nui.nvim",
},
config = function ()
require('neo-tree').setup {}
end,
}
2022-11-21 12:47:24 +00:00
```
2024-02-26 15:03:53 +00:00
< / details >
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?
* 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 with `rm -rf ~/.local/share/nvim/`
2023-10-28 21:33:10 +00:00
* Can I keep my existing configuration in parallel to kickstart?
2023-11-30 22:30: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:
2023-10-28 21:33:10 +00:00
```
2023-11-30 22:30:55 +00:00
alias nvim-kickstart='NVIM_APPNAME="nvim-kickstart" nvim'
2023-10-28 21:33:10 +00:00
```
2023-11-30 22:30:55 +00:00
When you run Neovim using `nvim-kickstart` alias it will use the alternative config directory and the matching local directory `~/.local/share/nvim-kickstart` . You can apply this approach to any Neovim distribution that you would like to try out.
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
2023-11-03 18:04:25 +00:00
* Why is the kickstart `init.lua` a single file? Wouldn't it make sense to split it into multiple files?
* The main purpose of kickstart is to serve as a teaching tool and a reference
configuration that someone can easily `git clone` as a basis for their own.
As you progress in learning Neovim and Lua, you might consider splitting `init.lua`
into smaller parts. A fork of kickstart that does this while maintaining the exact
same functionality is available here:
* [kickstart-modular.nvim ](https://github.com/dam9000/kickstart-modular.nvim )
* Discussions on this topic can be found here:
* [Restructure the configuration ](https://github.com/nvim-lua/kickstart.nvim/issues/218 )
* [Reorganize init.lua into a multi-file setup ](https://github.com/nvim-lua/kickstart.nvim/pull/473 )
2023-02-17 21:31:57 +00:00
### Windows Installation
Installation may require installing build tools, and updating the run command for `telescope-fzf-native`
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:
- Install CMake, and the Microsoft C++ Build Tools on Windows
```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-03 02:12:55 +00:00
Alternatively one can install gcc and make which don't require changing the config,
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
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 ](#Install-Kickstart ) step.