Over the past few years, Vim has changed. It has grown and morphed into a more modern piece of software. Something that’s responsive and features rich. If you’re like me and been using Vim 7.4 for years and years, it came with great surprise that newer and better versions came to be. _When talking about Vim, most people see it as this old, obsolete piece of software from the last century._hackernoon.com Modern Day Vim In this piece let’s talk about how we can migrate from Vim 7.4 to a modern version of Vim (Vim 8, Neovim). Let’s focus on switching to Neovim, because switching to Vim 8 should be almost effortless. The configuration files will be on the same place and once installed it should be working with all your previous configs out of the box. There are two ways (using Linux) to install Vim 8: Using the unofficial PPA: sudo apt-add-repository ppa:jonathonf/vim sudo apt update sudo apt install vim 2. Download the from the official website and build it on your own. latest version For Mac Os users, should be enough. brew upgrade vim Even though Neovim is a fork of Vim, it’s not exactly the same thing. We could argue it is a totally different piece of software, but that would be somewhat radical. But because it’s different, it has a different way of installing. Once again, we can either use the PPA: sudo apt-add-repository ppa:neovim-ppa/stable sudo apt update sudo apt install neovim Or use the package manager: sudo apt install neovim. For Mac OS user, of course: brew install neovim Neovim is not Vim, and because of that, using to launch it will not work. The better you’ll get with that command is an outdated version of Vim or Vim 8 if you happen to have it installed. The correct command to launch Neovim is $vim $nvim. There are ways to make the command behave like . It involves turning it into an alias for . There are loads of resources for doing that all over the internet, but making the change in your head shouldn’t be complicated. $vim $nvim $nvim One thing that will definitely make our life harder is the fact that all Vim configuration resides on . But Neovim uses ~/.vimrc ~/.config/nvim/init.vim by default. Because we’re all lazy and don’t want to have configuration files duplicated all over our file system, there’s the option to create a with the following content: ~/.config/nvim/init.vim set runtimepath^=/.vim runtimepath+=~/.vim/after let &packpath = &runtimepath source ~/.vimrc What this code does is everytime you launch nvim it searches for your .vimrc file and sources it. This way all your already existing configurations will be still running on Neovim. And by the way, Congratulations, you just switched to Neovim! Having trouble with Vim? Don’t know what to put into your .vimrc file? Want to use it for programming? Check out my new book “An IDE Called Vim”. It goes through all the basics of Vim, from installing to using it as an IDE.

Changing to Neovim

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

7 Things You Should Know about Vim

5 Vim Plugins I Can’t Live Without for Javascript Development

A Beginner's Guide to Vim

My neovim setup for Go

Pros and Cons of Vim in 2018

Transforming Vim to a Complete IDE with NeoVim: From Laggy to Efficient

7 Things You Should Know about Vim

5 Vim Plugins I Can’t Live Without for Javascript Development

A Beginner's Guide to Vim

My neovim setup for Go

Pros and Cons of Vim in 2018

Transforming Vim to a Complete IDE with NeoVim: From Laggy to Efficient

Light-Mode

Classic

Newspaper

Minty

Dark-Mode

Neon Noir

Minty

HN StartUps