Plugins 101

Vim (and especially Neovim) comes bare by default, on purpose. Plugins fill the gaps, but you don’t need dozens of them. This chapter covers a plugin manager and three plugins genuinely worth having as a beginner.

What a plugin manager does

A plugin manager installs, updates, and loads plugins for you, so you’re not manually downloading files and figuring out where Vim expects them. For classic Vim, vim-plug is a solid, simple choice. For Neovim, lazy.nvim is the current standard and handles lazy-loading (only loading a plugin once you actually need it) automatically.

Installation steps differ by manager and change over time, so follow the current instructions on the plugin manager’s own page rather than a fixed set of steps here. Both are a matter of adding a few lines to your config file and running one command.

Three plugins worth installing first

A fuzzy finder (such as fzf.vim for Vim, or telescope.nvim for Neovim) lets you find and open files by typing part of their name, instead of navigating folders by hand. This alone changes how fast you move around a project.

A file explorer (such as NERDTree or nvim-tree ) gives you a sidebar showing the folder structure, closer to what you’re used to in other editors, for the moments when browsing by eye is faster than searching by name.

A status line (such as lightline.vim or lualine.nvim ) replaces Vim’s plain bottom bar with one that shows your mode, file name, and position more clearly at a glance.

Neovim note: if you’re on Neovim, its built-in LSP (Language Server Protocol) support means you can get autocomplete, go-to-definition, and inline errors for most programming languages without a heavyweight plugin, just a small amount of setup per language. Classic Vim can do this too through plugins like coc.nvim, but Neovim’s version ships closer to built in.

A word of caution

It’s tempting to install fifteen plugins in your first week because a blog post said they’re essential. Don’t. Every plugin is one more thing that can break, conflict, or slow down startup, and you won’t yet know enough about your own workflow to judge which ones actually help you. Start with the three above, use them for a couple of weeks, and add more only when you notice a specific gap.

Try it

  1. Install a plugin manager (vim-plug for Vim, lazy.nvim for Neovim), following the current setup instructions on its page.
  2. Add one plugin, a fuzzy finder is the best first pick, to your config file and install it.
  3. Use it to open a file by typing part of its name instead of using :e.
  4. Wait at least a few days of regular use before adding a second plugin.

← Configuring Vim