@ -24,7 +24,7 @@ If you are experiencing issues, please make sure you have the latest versions.
External Requirements:
- Basic utils: `git` , `make` , `unzip` , C Compiler (`gcc`)
- [ripgrep ](https://github.com/BurntSushi/ripgrep#installation )
- Clipboard tool (xclip/xsel/win32yank or other depending on platform)
- Clipboard tool (xclip/xsel/win32yank or other depending on the platform)
- A [Nerd Font ](https://www.nerdfonts.com/ ): optional, provides various icons
- if you have it set `vim.g.have_nerd_font` in `init.lua` to true
- Language Setup:
@ -56,12 +56,12 @@ so that you have your own copy that you can modify, then install by cloning the
fork to your machine using one of the commands below, depending on your OS.
> **NOTE**
> Your fork's url will be something like this:
> Your fork's URL will be something like this:
> `https://github.com/<your_github_username>/kickstart.nvim.git`
You likely want to remove `lazy-lock.json` from your fork's `.gitignore` file
too - it's ignored in the kickstart repo to make maintenance easier, but it's
[recomm m ended to track it in version control](https://lazy.folke.io/usage/lockfile ).
[recomm ended to track it in version control](https://lazy.folke.io/usage/lockfile ).
#### Clone kickstart.nvim
> **NOTE**
@ -101,12 +101,17 @@ nvim
```
That's it! Lazy will install all the plugins you have. Use `:Lazy` to view
current plugin status. Hit `q` to close the window.
the current plugin status. Hit `q` to close the window.
#### Read The Friendly Documentation
Read through the `init.lua` file in your configuration folder for more
information about extending and exploring Neovim. That also includes
examples of adding popularly requested plugins.
> [!NOTE]
> For more information about a particular plugin check its repository's documentation.
### Getting Started
@ -114,9 +119,9 @@ examples of adding popularly requested plugins.
### FAQ
* What should I do if I already have a pre-existing n eovim configuration?
* What should I do if I already have a pre-existing N eovim configuration?
* You should back it up and then delete all associated files.
* This includes your existing init.lua and the n eovim files in `~/.local`
* This includes your existing init.lua and the N eovim files in `~/.local`
which can be deleted with `rm -rf ~/.local/share/nvim/`
* Can I keep my existing configuration in parallel to kickstart?
* Yes! You can use [NVIM_APPNAME ](https://neovim.io/doc/user/starting.html#%24NVIM_APPNAME )`=nvim-NAME`
@ -135,7 +140,7 @@ examples of adding popularly requested plugins.
* The main purpose of kickstart is to serve as a teaching tool and a reference
configuration that someone can easily use to `git clone` as a basis for their own.
As you progress in learning Neovim and Lua, you might consider splitting `init.lua`
into smaller parts. A fork of kickstart that does this while maintaining the
into smaller parts. A fork of kickstart that does this while maintaining the
same functionality is available here:
* [kickstart-modular.nvim ](https://github.com/dam9000/kickstart-modular.nvim )
* Discussions on this topic can be found here:
@ -174,7 +179,7 @@ run in cmd as **admin**:
winget install --accept-source-agreements chocolatey.chocolatey
```
2. install all requirements using choco, exit previous cmd and
2. install all requirements using choco, exit the previous cmd and
open a new one so that choco path is set, and run in cmd as **admin** :
```
choco install -y neovim git ripgrep wget fd unzip gzip mingw make