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
65
+
> `nvim-lua` with `<your_github_username>` in the commands below
52
66
53
67
<details><summary> Linux and Mac </summary>
54
68
@@ -83,93 +97,34 @@ nvim
83
97
```
84
98
85
99
That's it! Lazy will install all the plugins you have. Use `:Lazy` to view
86
-
current plugin status.
100
+
current plugin status. Hit `q` to close the window.
87
101
88
102
Read through the `init.lua` file in your configuration folder for more
89
-
information about extending and exploring Neovim.
103
+
information about extending and exploring Neovim. That also includes
104
+
examples of adding popularly requested plugins.
105
+
90
106
91
107
### Getting Started
92
108
93
109
[The Only Video You Need to Get Started with Neovim](https://youtu.be/m8C0Cq9Uv9o)
94
110
95
-
### Recommended Steps
96
-
97
-
[Fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) this repo
98
-
(so that you have your own copy that you can modify) and then install. You
99
-
can install it on your machine using the methods above.
100
-
101
-
> **NOTE**
102
-
> Your fork's url will be something like this: `https://github.com/<your_github_username>/kickstart.nvim.git`
103
-
104
-
#### Examples of adding popularly requested plugins
105
-
106
-
NOTE: You'll need to uncomment the line in the init.lua that turns on loading custom plugins.
107
-
108
-
<details>
109
-
<summary>Adding autopairs</summary>
110
-
111
-
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
-
113
-
In the file: `lua/custom/plugins/autopairs.lua`, add:
114
-
115
-
```lua
116
-
-- File: lua/custom/plugins/autopairs.lua
117
-
118
-
return {
119
-
"windwp/nvim-autopairs",
120
-
-- Optional dependency
121
-
dependencies= { 'hrsh7th/nvim-cmp' },
122
-
config=function()
123
-
require("nvim-autopairs").setup {}
124
-
-- If you want to automatically add `(` after selecting a function or method
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).
140
-
141
-
In the file: `lua/custom/plugins/filetree.lua`, add:
142
-
143
-
```lua
144
-
-- File: lua/custom/plugins/filetree.lua
145
-
146
-
return {
147
-
"nvim-neo-tree/neo-tree.nvim",
148
-
version="*",
149
-
dependencies= {
150
-
"nvim-lua/plenary.nvim",
151
-
"nvim-tree/nvim-web-devicons", -- not strictly required, but recommended
152
-
"MunifTanjim/nui.nvim",
153
-
},
154
-
config=function ()
155
-
require('neo-tree').setup {}
156
-
end,
157
-
}
158
-
```
159
-
160
-
</details>
161
-
162
111
### FAQ
163
112
164
113
* What should I do if I already have a pre-existing neovim configuration?
165
114
* You should back it up and then delete all associated files.
166
-
* This includes your existing init.lua and the neovim files in `~/.local` which can be deleted with `rm -rf ~/.local/share/nvim/`
115
+
* This includes your existing init.lua and the neovim files in `~/.local`
116
+
which can be deleted with `rm -rf ~/.local/share/nvim/`
167
117
* 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:
118
+
* Yes! You can use [NVIM_APPNAME](https://neovim.io/doc/user/starting.html#%24NVIM_APPNAME)`=nvim-NAME`
119
+
to maintain multiple configurations. For example, you can install the kickstart
120
+
configuration in `~/.config/nvim-kickstart` and create an alias:
169
121
```
170
122
alias nvim-kickstart='NVIM_APPNAME="nvim-kickstart" nvim'
171
123
```
172
-
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.
124
+
When you run Neovim using `nvim-kickstart` alias it will use the alternative
125
+
config directory and the matching local directory
126
+
`~/.local/share/nvim-kickstart`. You can apply this approach to any Neovim
127
+
distribution that you would like to try out.
173
128
* What if I want to "uninstall" this configuration:
174
129
* See [lazy.nvim uninstall](https://github.com/folke/lazy.nvim#-uninstalling) information
175
130
* Why is the kickstart `init.lua` a single file? Wouldn't it make sense to split it into multiple files?
0 commit comments