@@ -24,7 +24,7 @@ If you are experiencing issues, please make sure you have the latest versions.
24
24
External Requirements:
25
25
- Basic utils: ` git ` , ` make ` , ` unzip ` , C Compiler (` gcc ` )
26
26
- [ 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)
28
28
- A [ Nerd Font] ( https://www.nerdfonts.com/ ) : optional, provides various icons
29
29
- if you have it set ` vim.g.have_nerd_font ` in ` init.lua ` to true
30
30
- Language Setup:
@@ -56,12 +56,12 @@ so that you have your own copy that you can modify, then install by cloning the
56
56
fork to your machine using one of the commands below, depending on your OS.
57
57
58
58
> ** NOTE**
59
- > Your fork's url will be something like this:
59
+ > Your fork's URL will be something like this:
60
60
> ` https://github.com/<your_github_username>/kickstart.nvim.git `
61
61
62
62
You likely want to remove ` lazy-lock.json ` from your fork's ` .gitignore ` file
63
63
too - it's ignored in the kickstart repo to make maintenance easier, but it's
64
- [ recommmended to track it in version control] ( https://lazy.folke.io/usage/lockfile ) .
64
+ [ recommended to track it in version control] ( https://lazy.folke.io/usage/lockfile ) .
65
65
66
66
#### Clone kickstart.nvim
67
67
> ** NOTE**
101
101
```
102
102
103
103
That's it! Lazy will install all the plugins you have. Use ` :Lazy ` to view
104
- current plugin status. Hit ` q ` to close the window.
104
+ the current plugin status. Hit ` q ` to close the window.
105
105
106
106
Read through the ` init.lua ` file in your configuration folder for more
107
107
information about extending and exploring Neovim. That also includes
@@ -114,9 +114,9 @@ examples of adding popularly requested plugins.
114
114
115
115
### FAQ
116
116
117
- * What should I do if I already have a pre-existing neovim configuration?
117
+ * What should I do if I already have a pre-existing Neovim configuration?
118
118
* You should back it up and then delete all associated files.
119
- * This includes your existing init.lua and the neovim files in ` ~/.local `
119
+ * This includes your existing init.lua and the Neovim files in ` ~/.local `
120
120
which can be deleted with ` rm -rf ~/.local/share/nvim/ `
121
121
* Can I keep my existing configuration in parallel to kickstart?
122
122
* Yes! You can use [ NVIM_APPNAME] ( https://neovim.io/doc/user/starting.html#%24NVIM_APPNAME ) ` =nvim-NAME `
@@ -174,7 +174,7 @@ run in cmd as **admin**:
174
174
winget install --accept-source-agreements chocolatey.chocolatey
175
175
```
176
176
177
- 2 . install all requirements using choco, exit previous cmd and
177
+ 2 . install all requirements using choco, exit the previous cmd and
178
178
open a new one so that choco path is set, and run in cmd as ** admin** :
179
179
```
180
180
choco install -y neovim git ripgrep wget fd unzip gzip mingw make
0 commit comments