Neovim

Neovim provides editing, windows, terminals and language-client facilities. LazyVim packages plugins, bindings and configuration conventions into a distribution. It reduces initial assembly but does not remove the need to understand file types, project roots, external tools and versions.

This series assumes terminal familiarity. If Vim editing is new, complete :Tutor first: insert text, return to normal mode, save and exit.

Reading path

Use individual chapters for an existing setup. New users should complete the project task before adding optional plugins.

Check prerequisites

nvim --version
git --version
rg --version

Compare the installed version and external dependencies with LazyVim's current requirements. Fonts affect icons; compilers may build parsers or native plugins; SDKs depend on the project.

Configuration conventions here reference LazyVim 16. The maintenance machine uses a Neovim 0.13 development build, which is not a requirement for readers. Record exact versions when troubleshooting API differences.

Try an isolated configuration

On Linux/macOS, use NVIM_APPNAME to separate a learning setup. The destination must not already exist:

git clone https://github.com/LazyVim/starter ~/.config/nvim-lab

Launch it:

NVIM_APPNAME=nvim-lab nvim

First startup downloads plugins and needs network access and build tools. Use the same application name each time; plain nvim still uses the normal configuration. Do not delete the existing setup to test a configuration idea. Installation

Windows paths differ. Query actual locations inside Neovim:

:lua print(vim.fn.stdpath("config"))
:lua print(vim.fn.stdpath("data"))

The first is configuration; the second normally contains plugin data.

Configuration responsibilities

nvim-lab/
├── init.lua
├── lazyvim.json
├── lazy-lock.json
└── lua/
    ├── config/
    │   ├── lazy.lua
    │   ├── options.lua
    │   ├── keymaps.lua
    │   └── autocmds.lua
    └── plugins/
        └── editing.lua

init.lua enters configuration; lazy.lua initialises plugin management; options.lua, keymaps.lua and autocmds.lua hold options, mappings and event responses. Files under lua/plugins/ return plugin specifications. lazyvim.json records extras and lazy-lock.json pins plugin commits.

Use :LazyExtras to inspect and enable language support, then complete installation and restart as instructed. Optional integrations and external SDKs are not guaranteed to be installed by selecting an extra.

Verify the first startup

Run :LazyHealth, then inspect task-relevant :checkhealth results. An unrelated optional provider need not block editing, but missing tools for the selected language do matter.

Place basic options in lua/config/options.lua:

vim.opt.number = true
vim.opt.relativenumber = true
vim.g.autoformat = false

Disabling automatic formatting helps make changes visible while learning. Restore project-appropriate behaviour later; see language tools.

Preparation is complete when you can open and save files, identify the configuration directory and explain relevant health-check failures. Continue with editing and navigation, then verify everything through the project exercise.