Install Neovim from the Linux Mint repository

The fastest way to get Neovim running on Linux Mint is through the built-in package manager. Open a terminal and run:

sudo apt update followed by sudo apt install neovim. This pulls Neovim from Mint's repositories, which usually carry a recent stable version. The installation finishes in under a minute on most systems.

Once installed, type nvim in the terminal to launch the editor. You will see Neovim's welcome screen with basic navigation hints. Press :q and then Enter to exit.

Key Takeaways

  • The repository method (sudo apt install neovim) is the simplest route and works for most users who want a stable version.
  • If you need a newer version than the repository offers, you can download a pre-built binary directly from the Neovim GitHub releases page.
  • Building from source takes longer but gives you the absolute latest code and is useful only if you plan to contribute or need unreleased features.
  • After installation, create a config file at ~/.config/nvim/init.vim or ~/.config/nvim/init.lua to customize keybindings and plugins.
  • Neovim reads configuration from the .config/nvim directory in your home folder, not from the old .vim location that regular Vim uses.

Install Neovim from a pre-built binary

If the repository version is too old for your needs, download a pre-built binary from the official Neovim releases page on GitHub. This method gives you a newer version without compiling.

Visit the Neovim GitHub releases page, find the latest release, and download the file named nvim.appimage. Save it to your home directory or a folder like ~/bin. Open a terminal in that folder and run chmod +x nvim.appimage to make it executable, then ./nvim.appimage to run it.

To use Neovim from anywhere in the terminal, move the file to a system path. Run sudo mv nvim.appimage /usr/local/bin/nvim. Now you can type nvim from any terminal window to launch the editor.

Build Neovim from source code

Building from source takes more time but gives you the latest development version and full control over the build. You will need a C compiler and Git installed first. Run sudo apt install build-essential git cmake to install these tools.

Clone the Neovim repository with git clone https://github.com/neovim/neovim.git, then move into the folder with cd neovim. Run make CMAKE_BUILD_TYPE=Release to compile. This step takes several minutes depending on your system speed.

Once compilation finishes, run sudo make install to place Neovim in your system path. Type nvim --version to confirm the installation worked and see which version you built.

Set up your configuration file

Neovim looks for configuration in ~/.config/nvim/ rather than the ~/.vim/ folder that regular Vim uses. Create this directory if it does not exist by running mkdir -p ~/.config/nvim.

Create a new configuration file with nvim ~/.config/nvim/init.vim for traditional Vim configuration syntax, or nvim ~/.config/nvim/init.lua if you prefer Lua. Start with basic settings like set number to show line numbers, or set tabstop=4 to control indentation width.

A minimal config file might look like this: set number, set expandtab, set tabstop=4, and set shiftwidth=4. Save the file by pressing Escape, then typing :wq and Enter. The next time you open Neovim, these settings will load automatically.

Install a plugin manager

Most Neovim users install plugins to extend functionality. The most common plugin managers are vim-plug, packer.nvim, and lazy.nvim. vim-plug works with both Vim and Neovim and is straightforward to set up.

To install vim-plug, run curl -fLo ~/.local/share/nvim/site/autoload/plug.vim --create-dirs https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim. This downloads the plugin manager to the correct location.

Edit your init.vim file and add a plugins section between call plug#begin() and call plug#end(). For example, to add the popular vim-sensible plugin, add the line Plug 'tpope/vim-sensible' between those markers. Save the file, open Neovim, and run :PlugInstall to download and install the plugins you listed.

Verify your installation and test basic commands

After installation, confirm everything works by opening Neovim and checking the version. Type nvim --version in a terminal to see the version number and build information. This also tells you which Lua version is included, which matters if you plan to write Lua configuration.

Open a test file with nvim test.txt and practice basic navigation: press i to enter insert mode, type some text, press Escape to return to normal mode, then type :wq and Enter to save and exit. These are the core movements you will use constantly.

Check that your configuration loaded by running :set number and looking for line numbers on the left side. If they appear, your init.vim or init.lua file is being read correctly. If not, verify the file exists at ~/.config/nvim/init.vim or ~/.config/nvim/init.lua.

Frequently Asked Questions

What is the difference between Neovim and regular Vim?

Neovim is a fork of Vim that modernizes the codebase and adds features like built-in language server support, better plugin architecture, and Lua scripting. Most Vim configuration works in Neovim, but Neovim adds new capabilities that regular Vim does not have. If you already know Vim, Neovim will feel familiar.

Can I use my existing Vim configuration with Neovim?

Mostly yes, but Neovim looks in a different location. Move your .vimrc file to ~/.config/nvim/init.vim and it should work. Some older plugins may not be compatible, but most modern ones support both editors. Test your configuration after moving it and check for error messages when Neovim starts.

Which installation method should I choose?

Use the repository method (apt install) if you want stability and do not need the latest features. Use the pre-built binary if the repository version is too old. Use source compilation only if you are contributing to Neovim development or need unreleased features.

How do I uninstall Neovim if I change my mind?

If you installed via the repository, run sudo apt remove neovim. If you used the AppImage binary, delete the file you downloaded. If you built from source, navigate to the neovim folder and run sudo make uninstall. Your configuration files in ~/.config/nvim/ will remain unless you delete them manually.

Why does Neovim look for config in .config instead of .vim?

Neovim follows the XDG Base Directory specification, which is a Linux standard for where applications store configuration. This keeps your home directory cleaner and separates Neovim config from regular Vim. You can still use .vim folders for plugins if you set the right paths in your config file.