@@ -24,12 +24,12 @@ If you are experiencing issues, please make sure you have the latest versions.
2424External Requirements:
2525- Basic utils: ` git ` , ` make ` , ` unzip ` , C Compiler (` gcc ` )
2626- [ ripgrep] ( https://github.com/BurntSushi/ripgrep#installation )
27- - Clipboard tool (xclip/xsel/win32yank or other depending on platform)
27+ - Clipboard tool (xclip/xsel/win32yank or other depending on the platform)
2828- A [ Nerd Font] ( https://www.nerdfonts.com/ ) : optional, provides various icons
2929 - if you have it set ` vim.g.have_nerd_font ` in ` init.lua ` to true
3030- Language Setup:
31- - If want to write Typescript, you need ` npm `
32- - If want to write Golang, you will need ` go `
31+ - If you want to write Typescript, you need ` npm `
32+ - If you want to write Golang, you will need ` go `
3333 - etc.
3434
3535> ** NOTE**
@@ -46,8 +46,8 @@ Neovim's configurations are located under the following paths, depending on your
4646| OS | PATH |
4747| :- | :--- |
4848| Linux, MacOS | ` $XDG_CONFIG_HOME/nvim ` , ` ~/.config/nvim ` |
49- | Windows (cmd)| ` %userprofile%\AppData\Local \nvim\ ` |
50- | Windows (powershell)| ` $env:USERPROFILE\AppData\Local \nvim\ ` |
49+ | Windows (cmd)| ` %localappdata% \nvim\ ` |
50+ | Windows (powershell)| ` $env:LOCALAPPDATA \nvim\ ` |
5151
5252#### Recommended Step
5353
@@ -56,9 +56,13 @@ so that you have your own copy that you can modify, then install by cloning the
5656fork to your machine using one of the commands below, depending on your OS.
5757
5858> ** NOTE**
59- > Your fork's url will be something like this:
59+ > Your fork's URL will be something like this:
6060> ` https://github.com/<your_github_username>/kickstart.nvim.git `
6161
62+ You likely want to remove ` lazy-lock.json ` from your fork's ` .gitignore ` file
63+ too - it's ignored in the kickstart repo to make maintenance easier, but it's
64+ [ recommended to track it in version control] ( https://lazy.folke.io/usage/lockfile ) .
65+
6266#### Clone kickstart.nvim
6367> ** NOTE**
6468> If following the recommended step above (i.e., forking the repo), replace
@@ -77,13 +81,13 @@ git clone https://github.com/nvim-lua/kickstart.nvim.git "${XDG_CONFIG_HOME:-$HO
7781If you're using ` cmd.exe ` :
7882
7983```
80- git clone https://github.com/nvim-lua/kickstart.nvim.git %userprofile%\AppData\Local\ nvim\
84+ git clone https://github.com/nvim-lua/kickstart.nvim.git "%localappdata%\ nvim"
8185```
8286
8387If you're using ` powershell.exe `
8488
8589```
86- git clone https://github.com/nvim-lua/kickstart.nvim.git $ env:USERPROFILE\AppData\Local\ nvim\
90+ git clone https://github.com/nvim-lua/kickstart.nvim.git "${ env:LOCALAPPDATA}\ nvim"
8791```
8892
8993</details >
@@ -97,22 +101,27 @@ nvim
97101```
98102
99103That's it! Lazy will install all the plugins you have. Use ` :Lazy ` to view
100- current plugin status. Hit ` q ` to close the window.
104+ the current plugin status. Hit ` q ` to close the window.
105+
106+ #### Read The Friendly Documentation
101107
102108Read through the ` init.lua ` file in your configuration folder for more
103109information about extending and exploring Neovim. That also includes
104110examples of adding popularly requested plugins.
105111
112+ > [ !NOTE]
113+ > For more information about a particular plugin check its repository's documentation.
114+
106115
107116### Getting Started
108117
109118[ The Only Video You Need to Get Started with Neovim] ( https://youtu.be/m8C0Cq9Uv9o )
110119
111120### FAQ
112121
113- * What should I do if I already have a pre-existing neovim configuration?
122+ * What should I do if I already have a pre-existing Neovim configuration?
114123 * You should back it up and then delete all associated files.
115- * This includes your existing init.lua and the neovim files in ` ~/.local `
124+ * This includes your existing init.lua and the Neovim files in ` ~/.local `
116125 which can be deleted with ` rm -rf ~/.local/share/nvim/ `
117126* Can I keep my existing configuration in parallel to kickstart?
118127 * Yes! You can use [ NVIM_APPNAME] ( https://neovim.io/doc/user/starting.html#%24NVIM_APPNAME ) ` =nvim-NAME `
@@ -126,12 +135,12 @@ examples of adding popularly requested plugins.
126135 `~/.local/share/nvim-kickstart`. You can apply this approach to any Neovim
127136 distribution that you would like to try out.
128137* What if I want to "uninstall" this configuration:
129- * See [lazy.nvim uninstall](https://github.com/ folke/lazy.nvim #-uninstalling) information
138+ * See [lazy.nvim uninstall](https://lazy. folke.io/usage #-uninstalling) information
130139* Why is the kickstart `init.lua` a single file? Wouldn't it make sense to split it into multiple files?
131140 * The main purpose of kickstart is to serve as a teaching tool and a reference
132141 configuration that someone can easily use to `git clone` as a basis for their own.
133142 As you progress in learning Neovim and Lua, you might consider splitting `init.lua`
134- into smaller parts. A fork of kickstart that does this while maintaining the
143+ into smaller parts. A fork of kickstart that does this while maintaining the
135144 same functionality is available here:
136145 * [kickstart-modular.nvim](https://github.com/dam9000/kickstart-modular.nvim)
137146 * Discussions on this topic can be found here:
@@ -170,7 +179,7 @@ run in cmd as **admin**:
170179winget install --accept-source-agreements chocolatey.chocolatey
171180```
172181
173- 2 . install all requirements using choco, exit previous cmd and
182+ 2 . install all requirements using choco, exit the previous cmd and
174183open a new one so that choco path is set, and run in cmd as ** admin** :
175184```
176185choco install -y neovim git ripgrep wget fd unzip gzip mingw make
0 commit comments