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
@@ -87,17 +89,15 @@ information about extending and exploring Neovim.
87
89
88
90
### Getting Started
89
91
90
-
See [Effective Neovim: Instant IDE](https://youtu.be/stqUbv-5u2s), covering the
91
-
previous version. Note: The install via init.lua is outdated, please follow the
92
-
install instructions in this file instead. An updated video is coming soon.
92
+
[The Only Video You Need to Get Started with Neovim](https://youtu.be/m8C0Cq9Uv9o)
93
93
94
94
### Recommended Steps
95
95
96
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 installing you
98
-
can install to your machine using the methods above.
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
99
100
-
> **NOTE**
100
+
> **NOTE**
101
101
> Your fork's url will be something like this: `https://github.com/<your_github_username>/kickstart.nvim.git`
102
102
103
103
#### Examples of adding popularly requested plugins
@@ -135,13 +135,12 @@ return {
135
135
<details>
136
136
<summary>Adding a file tree plugin</summary>
137
137
138
-
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.
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).
139
139
140
140
In the file: `lua/custom/plugins/filetree.lua`, add:
141
141
142
142
```lua
143
-
-- Unless you are still migrating, remove the deprecated commands from v1.x
144
-
vim.cmd([[ let g:neo_tree_remove_legacy_commands = 1 ]])
143
+
-- File: lua/custom/plugins/filetree.lua
145
144
146
145
return {
147
146
"nvim-neo-tree/neo-tree.nvim",
@@ -162,10 +161,10 @@ return {
162
161
### FAQ
163
162
164
163
* What should I do if I already have a pre-existing neovim configuration?
165
-
* You should back it up, then delete all files associated with it.
164
+
* You should back it up and then delete all associated files.
166
165
* This includes your existing init.lua and the neovim files in `~/.local` which can be deleted with `rm -rf ~/.local/share/nvim/`
167
166
* Can I keep my existing configuration in parallel to kickstart?
168
-
* 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:
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:
169
168
```
170
169
alias nvim-kickstart='NVIM_APPNAME="nvim-kickstart" nvim'
171
170
```
@@ -174,9 +173,9 @@ return {
174
173
* See [lazy.nvim uninstall](https://github.com/folke/lazy.nvim#-uninstalling) information
175
174
* Why is the kickstart `init.lua` a single file? Wouldn't it make sense to split it into multiple files?
176
175
* The main purpose of kickstart is to serve as a teaching tool and a reference
177
-
configuration that someone can easily `git clone` as a basis for their own.
176
+
configuration that someone can easily use to `git clone` as a basis for their own.
178
177
As you progress in learning Neovim and Lua, you might consider splitting `init.lua`
179
-
into smaller parts. A fork of kickstart that does this while maintaining the exact
178
+
into smaller parts. A fork of kickstart that does this while maintaining the
0 commit comments