You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> If following the recommended step above (i.e., forking the repo), replace
64
+
> `nvim-lua` with `<your_github_username>` in the commands below
51
65
52
66
<details><summary> Linux and Mac </summary>
53
67
@@ -82,23 +96,11 @@ nvim
82
96
```
83
97
84
98
That's it! Lazy will install all the plugins you have. Use `:Lazy` to view
85
-
current plugin status.
99
+
current plugin status. Hit `q` to close the window.
86
100
87
101
Read through the `init.lua` file in your configuration folder for more
88
102
information about extending and exploring Neovim.
89
103
90
-
### Getting Started
91
-
92
-
[The Only Video You Need to Get Started with Neovim](https://youtu.be/m8C0Cq9Uv9o)
93
-
94
-
### Recommended Steps
95
-
96
-
[Fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) this repo
97
-
(so that you have your own copy that you can modify) and then install. You
98
-
can install it on your machine using the methods above.
99
-
100
-
> **NOTE**
101
-
> Your fork's url will be something like this: `https://github.com/<your_github_username>/kickstart.nvim.git`
102
104
103
105
#### Examples of adding popularly requested plugins
104
106
@@ -107,7 +109,9 @@ NOTE: You'll need to uncomment the line in the init.lua that turns on loading cu
107
109
<details>
108
110
<summary>Adding autopairs</summary>
109
111
110
-
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).
112
+
This will automatically install [windwp/nvim-autopairs](https://github.com/windwp/nvim-autopairs)
113
+
and enable it on startup. For more information, see documentation for
114
+
[lazy.nvim](https://github.com/folke/lazy.nvim).
111
115
112
116
In the file: `lua/custom/plugins/autopairs.lua`, add:
113
117
@@ -135,7 +139,9 @@ return {
135
139
<details>
136
140
<summary>Adding a file tree plugin</summary>
137
141
138
-
This will install the tree plugin and add the command `:Neotree` for you. For more information, see the documentation at [neo-tree.nvim](https://github.com/nvim-neo-tree/neo-tree.nvim).
142
+
This will install the tree plugin and add the command `:Neotree` for you.
In the file: `lua/custom/plugins/filetree.lua`, add:
141
147
@@ -158,17 +164,27 @@ return {
158
164
159
165
</details>
160
166
167
+
### Getting Started
168
+
169
+
[The Only Video You Need to Get Started with Neovim](https://youtu.be/m8C0Cq9Uv9o)
170
+
161
171
### FAQ
162
172
163
173
* What should I do if I already have a pre-existing neovim configuration?
164
174
* You should back it up and then delete all associated files.
165
-
* This includes your existing init.lua and the neovim files in `~/.local` which can be deleted with `rm -rf ~/.local/share/nvim/`
175
+
* This includes your existing init.lua and the neovim files in `~/.local`
176
+
which can be deleted with `rm -rf ~/.local/share/nvim/`
166
177
* Can I keep my existing configuration in parallel to kickstart?
167
-
* 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:
178
+
* Yes! You can use [NVIM_APPNAME](https://neovim.io/doc/user/starting.html#%24NVIM_APPNAME)`=nvim-NAME`
179
+
to maintain multiple configurations. For example, you can install the kickstart
180
+
configuration in `~/.config/nvim-kickstart` and create an alias:
168
181
```
169
182
alias nvim-kickstart='NVIM_APPNAME="nvim-kickstart" nvim'
170
183
```
171
-
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.
184
+
When you run Neovim using `nvim-kickstart` alias it will use the alternative
185
+
config directory and the matching local directory
186
+
`~/.local/share/nvim-kickstart`. You can apply this approach to any Neovim
187
+
distribution that you would like to try out.
172
188
* What if I want to "uninstall" this configuration:
173
189
* See [lazy.nvim uninstall](https://github.com/folke/lazy.nvim#-uninstalling) information
174
190
* Why is the kickstart `init.lua` a single file? Wouldn't it make sense to split it into multiple files?
@@ -182,8 +198,15 @@ return {
182
198
* [Restructure the configuration](https://github.com/nvim-lua/kickstart.nvim/issues/218)
183
199
* [Reorganize init.lua into a multi-file setup](https://github.com/nvim-lua/kickstart.nvim/pull/473)
184
200
185
-
### Windows Installation
201
+
### Install Recipes
202
+
203
+
Below you can find OS specific install instructions for Neovim and dependencies.
204
+
205
+
After installing all the dependencies continue with the [Install Kickstart](#Install-Kickstart) step.
186
206
207
+
#### Windows Installation
208
+
209
+
<details><summary>Windows with Microsoft C++ Build Tools and CMake</summary>
187
210
Installation may require installing build tools and updating the run command for `telescope-fzf-native`
188
211
189
212
See `telescope-fzf-native` documentation for [more details](https://github.com/nvim-telescope/telescope-fzf-native.nvim#installation)
0 commit comments