Learn Neovim - Pre-Requisite Skills & Environment Setup

#Introduction

Welcome to the Learn Neovim series! This series will take you from zero to production-ready Neovim mastery: starting with the philosophy of modal editing, Vim motions, fast navigation, registers & macros, Lua configuration (init.lua), the lazy.nvim plugin manager, Treesitter, LSP, autocompletion, all the way to a production-grade setup architecture in the upcoming episodes. There are 28 episodes in total that will guide you in building an ultra-fast editor as your daily driver.

But as the saying goes, "a sturdy house stands on a strong foundation". Before pressing the d key to delete text or writing your first Lua configuration, there are some basic skills and tools you must have and prepare first.

Why are these prerequisites so important? Neovim is an editor that runs inside the terminal and is configured using Lua. It is not a GUI application with clickable buttons — everything happens through the keyboard, commands, and text configuration files. In other words, if you are not yet comfortable with the terminal CLI or do not understand how text and files work at the system level, your learning journey will stall at every step. Imagine wanting to become a pilot but not understanding how to read cockpit instruments — no matter how great the plane is, taking off will still be difficult.

Episode 0 will be a roadmap to make sure you are all ready. We will cover the fundamental skills needed, prepare all the software (Neovim, a modern terminal, a Nerd Font, and supporting tooling), and then wrap up by verifying that everything works well. Once this episode is finished, you will be truly ready to move on to episode 1, which covers the history and background of why Neovim exists.

#Basic Skills You Must Have

Let's start with skills. Without these skills, no matter how sophisticated your tools are, they will be useless.

#Terminal & CLI Basics

Neovim was born and grew up in the Linux/Unix ecosystem, and it lives inside the terminal. Although it can run on Windows (natively or via WSL2), the majority of real-world usage — including on servers and in CI/CD — runs on Linux. That is why being able to operate the CLI is a hard requirement.

What should you master?

1. Navigation & file management. You should be comfortable switching directories, viewing contents, creating, copying, and deleting files. You will use this ability every day, including when managing the ~/.config/nvim/ configuration directory.

Navigation & file management

pwd                        # print current working directory
ls -la                     # list directory contents (including hidden files)
cd ~/.config/nvim          # go to the Neovim configuration directory
mkdir -p lua/config        # create nested directories
cp init.lua backup/init.lua # copy a file

2. Reading and processing text. Neovim works with plain text files, and when debugging we often need to filter long log output. You need to know commands such as cat, less, grep, and sed.

3. The PATH concept & environment variables. When you run nvim in the terminal, the shell looks for that binary in the directories registered in $PATH. If nvim is not found (the command not found error), most likely the binary has not been added to PATH. Understanding $PATH will save you from one of the most common mistakes in this episode.

4. Package managers. You must be able to install software through your distro's package manager, because that is the easiest way to install Neovim. On Ubuntu/Debian use apt, on Fedora/RHEL use dnf, on Arch use pacman, and on macOS use brew.

#Basic Text Editing Concepts

Neovim is a text editor, so understanding how text is represented on a computer is an important foundation. Some concepts you need to understand:

Why does this matter? Because everything you will do in Neovim — deleting lines, jumping to the next word, searching for patterns — is essentially manipulation of the cursor position relative to the text. Understanding that a file is a collection of lines and characters will make all the motion concepts in episode 2 feel intuitive.

#Software & Tools to Prepare

Neovim's hardware requirements are very simple — a regular laptop is enough. Here is the complete list of items we will prepare in this episode:

#Installing Neovim (v0.10+)

#Linux

On Linux, the easiest way is through the package manager. Make sure the version you get is at least 0.10.0. On some distros (for example Debian stable), the Neovim version in the official repository can lag behind — if you need the latest version, use the AppImage, a binary release, or a community maintainer package.

Ubuntu/Debian (apt)Fedora/RHEL (dnf)Arch (pacman)

sudo apt update && sudo apt install -y neovim

sudo dnf install -y neovim

sudo pacman -S neovim

#macOS

brew update
brew install neovim

#Windows

choco install neovim

scoop install neovim

#Verifying the Installation

Once installed, verify the version. Make sure it is at least NVIM v0.10.0:

nvim --version
 
NVIM v0.11.0
Build type: Release
...

If your version is older than 0.10.0, upgrade first before continuing this series.

#A Modern Terminal with True Color

Neovim is an editor inside the terminal — which means the quality of its display depends heavily on the terminal you use. A modern terminal that supports true color (24-bit) will make Neovim colorschemes look perfect. Older terminals that only support 256 colors will make colors look "washed out" (posterized) and unpleasant to look at.

Recommended modern terminals:

#Installing a Nerd Font

A Nerd Font is a font patched with thousands of glyphs/icons (chevrons, folders, git, programming language logos) needed by modern plugins such as nvim-web-devicons, lualine.nvim, and bufferline.nvim. Without a Nerd Font, those icons appear as empty boxes (tofu).

#Installing a Nerd Font

Recommendation: JetBrainsMono Nerd Font, FiraCode Nerd Font, or Hack Nerd Font. The easiest way is to download from the official Nerd Fonts website:

Install JetBrainsMono Nerd Font (Linux)

mkdir -p ~/.local/share/fonts
wget https://github.com/ryanoasis/nerd-fonts/releases/download/v3.2.1/JetBrainsMono.zip
unzip JetBrainsMono.zip -d ~/.local/share/fonts
fc-cache -fv ~/.local/share/fonts

Confirm the font is installed

fc-list | grep -i "JetBrainsMono"

After the font is installed, set it in your terminal settings (not in Neovim). In Ghostty for example:

font-family = JetBrainsMono Nerd Font
font-size = 13

#Supporting Tooling

Neovim itself is just an editor — its full power comes from the ecosystem of tools around it. Some required/recommended tools:

Install tooling (Ubuntu/Debian)

sudo apt install -y git make build-essential ripgrep fd-find unzip curl
curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash - && sudo apt install -y nodejs

#First Verification: Running Neovim

Once everything is installed, it is time for the first test. Run nvim in the terminal:

nvim
 
# Inside Neovim, check the health:
:checkhealth

When it first opens, Neovim shows a blank screen with help text. Do not worry if it looks "empty" — that is by design. Default Neovim is indeed almost bare; in the coming phases we will build a modern look through Lua configuration.

A few things to verify:

1. Neovim opens inside the terminal — it does not spawn a separate new window.
2. The help text displays correctly — no weird characters or boxes (if there are, your terminal font is not a Nerd Font yet).
3. Colors render smoothly — check with the following command:

:set termguicolors
:hi Normal guibg=#1e1e2e guifg=#cdd6f4

If the background turns a dark blue-gray (Catppuccin Mocha) with bright text and no harsh color "banding", your true color works well.

#Common Pitfalls

Here are the most common mistakes beginners make during setup:

1. The Neovim version is too old. Many people install from an old distro repository (e.g. Debian stable) and get Neovim 0.7/0.8. As a result, the newest plugins fail. Solution: make sure nvim --version shows at least 0.10.0.

2. The terminal does not support true color. The colorscheme looks "washed out" or the colors look strange. Solution: use a modern terminal (WezTerm, Kitty, Ghostty, Alacritty), not an ancient built-in terminal.

3. The terminal font was not switched to a Nerd Font. Plugin icons appear as empty boxes (□). Solution: install a Nerd Font and change the font in the terminal settings, then restart the terminal.

4. command not found: nvim. The binary is not found in $PATH. Solution: check the install location, add it to PATH in your shell config (~/.bashrc/~/.zshrc), then source it again or open a new terminal.

5. Neovim runs slowly on WSL2. The project folder is on a Windows path (/mnt/c/...) which has slow I/O. Solution: keep your projects in the Linux file system (~/...), not in /mnt/c.

6. Trying to learn everything at once. Neovim feels "uncomfortable" in the first week — that is normal. Do not rush to install 50 plugins before understanding the basics of modal editing.

#Closing

In episode 0 we prepared a solid foundation: we mastered two fundamental skills (terminal CLI and text editing concepts), installed Neovim v0.10+, set up a modern terminal with true color, installed a Nerd Font, and completed supporting tooling like git, make, gcc, ripgrep, fd, npm, and python3. We also verified that Neovim runs well in your terminal.

Key points to take with you:

• Neovim lives in the terminal — master the CLI basics and $PATH.
• Neovim is a pure text editor — all operations are based on cursor position and text patterns.
• Make sure Neovim v0.10+, a true color terminal, and a Nerd Font are installed correctly.
• Prepare the supporting tooling (git, make, gcc, rg, fd) because it will be used in the plugin phase.
• The most common setup mistakes are old versions, wrong fonts, and wrong PATH — check all three first if something goes wrong.

Make sure all the tools above are ready, because the next episode is all about concepts. In episode 1, we will discuss the history, background, and why you should choose Neovim — from the evolution of Vi (1976) → Vim (1991) → Neovim (2014), the advantages of Neovim's refactored architecture, to the modal editing philosophy that will change the way you write code. Stay motivated, because your Neovim learning journey has only just begun!