Over the summer, after finally getting around to learning Vim motions, I quickly fell down the Neovim rabbithole and have been procrastinating work by tinkering away at my configurations ever since! This post will be sharing setup that I have currently landed at to turn my Neovim editor into a supercharged workhorse.

by Geoff Greer

I know Vim better than most. Vim was my first real text editor. I used it for years. I helped write the Floobits plugin for Vim. I’ve delved into Vim’s source code to figure out its workings. I even helped write a patch (though it was rejected). Considering these credentials, I hope you’ll accept that I know what I’m talking about.

It may come as a shock when I say: The only good part of Vim is its user interface.

neovim is a project that seeks to aggressively refactor vim source code in order to achieve the following goals:

• Simplify maintenance to improve the speed that bug fixes and features get merged.
• Split the work between multiple developers.
• Enable the implementation of new/modern user interfaces without any modifications to the core source.
• Improve the extensibility power with a new plugin architecture based on coprocesses. Plugins will be written in any programming language without needing explicit support from the editor.

By achieving these goals, new developers will be more inclined to join the community, consequently improving the editor for all users.