Need a hand with tech consulting? I can help!
Learn more about how we can work via black.af .

The ecosystems of the world are dying.
Reduce your :pig::chicken: meat and :cow::goat: dairy intake to help the environment :seedling: .

This site is in the process of moving to Koype. You can view my instance at v2.jacky.wtf.

Neovim 0.1.0 Dropped - And It’s Fire

You know me. I really dig Vim and since then, I’ve moved to Neovim. But son, check out the features and things going down with Neovim 0.1.0.

:pencil: by Jacky Alciné Jacky Alciné :book: an software post :bookmark: vim , neovim , omg :clock7: written :eyeglasses: about 7 minutes, 1354 words :link: Comments - 0 Mention(s) - Permalink

So it happened. Neovim 0.1.0 is out. It’s the first minor version of Neovim since it began a while back as a fork of the fork of Vi. To be honest, I played with the idea of it when I first saw the alert in March 2015. I’ve used it passively for quite some time and didn’t really realize how awesome the shift was until someone mentioned it to me1. There’s a few things about neovim that I like a lot and some things I wish I saw sooner.

The Configuration MOVED

Since I work against a development version of neovim on my personal machine, I routinely let it be automatically updated as part of my system’s routine updates. I wasn’t paying attention to which packages were being updated2 and of course, didn’t have apt-listchanges installed. After tugging on my hair for a few minutes and grumbling, I entered :h vim-differences into Vim and saw this under the tagnvim-configuration:

- Use `$XDG_CONFIG_HOME/nvim/init.vim` instead of `.vimrc` for storing
- Use `$XDG_CONFIG_HOME/nvim` instead of `.vim` to store configuration files.
- Use `$XDG_DATA_HOME/shada/main.shada` instead of `.viminfo` for persistent
  session information.

This change was a big yet simple one. Yeah, sure, it’s just moving files but options in my Vim setup make the hard assumption that everything lives under $HOME/.vim. Running :h nvim-from-vim opened up with this:

Neovim is emphatically a fork of Vim, so compatibility to Vim should be pretty

To start the transition, link your previous configuration so Neovim can use
    mkdir -p ${XDG_CONFIG_HOME:=$HOME/.config}
    ln -s ~/.vim $XDG_CONFIG_HOME/nvim
    ln -s ~/.vimrc $XDG_CONFIG_HOME/nvim/init.vim

See, me, I didn’t want to bother with linking stuff over. I ended up just moving my configuration files over. Crisis averted.

Bunch of Options Dropped

This is one thing that got me really glad about Neovim. A lot of the default options that people had to change in vanilla Vim now are being set as the defacto setting (if not dropped altogether). The whole set of options won’t be completed until the 0.2 drop. It’s also a really fantastic use of a meta-issue for a feature checklist in Github. Kudos there to the Neovim team. Things like history, mouse and autoindent are all being set to more sensible defaults. This means less overriding in your root configuration file and more predictability when sharing someone else’s Vim setup. This means pair programming could be less “how do I do this?” and more “this code looks great!”

Job Control

Now this is probably something that won’t get much acclaim and but the concept of job control is :fire:. I mentioned it implicitly earlier but here’s a case example why it’d be handy. With my Vim plugin for CMake, a lot of text processing has to be done. Also the work of having a cache to persist information is needed to make sure information that’s dependent on other files and their content is updated when it happens. This helps with updating tag files, auto completion, path expansion and other features that could handle development. This function cmake#targets#cache handles all of that initial state building:

func! cmake#targets#cache()
  for aTarget in cmake#targets#list()
    let files = cmake#targets#files(aTarget)

    if empty(files)

    for aFile in files
      let shorter_name = fnamemodify(aFile, ':r')
      let shortest_name = fnamemodify(aFile, ':t:r')
      let g:cmake_cache.files[aFile] = aTarget

      if !empty(shorter_name) && !has_key(g:cmake_cache.files,shorter_name)
        let g:cmake_cache.files[shorter_name] = aTarget

      if !empty(shortest_name) && !has_key(g:cmake_cache.files,shortest_name)
        let g:cmake_cache.files[shortest_name] = aTarget

Loop in loop in loop3 :anguished:. But this gives a wealth of information to your client about the flags that each source file would need, what kind of options CMake is using, etc. Each of these functions do heavy recursive work and can seriously slow down Vim if you have more than 10 source files4. If you want, you can help me out; I’d appreciate it.

The New Suite of Plugins

I use a lot of plugins. So I think I have a decent-ish idea of what works for me and plays nice with others. This list is not going to be comprehensive; it’ll just talk about plugins I use a lot that are taking advantage of Neovim’s features.


Unite is an abstract text discovery tool for Vim. I say text and not file because it, at its core, provides an interface to look for text that satisfy a particular criteria. Now, this plugin isn’t new, but it does make use of neovim’s async task dispatching (via job control) to do file discovery over huge directories (via file_rec/neovim).


Neomake works in a similar fashion to Syntastic. Syntastic takes a currently provided file and runs it against a linting process. When said process is completed, it then populates the quickfix or locationlist windows in Vim for your review. The thing about this is that typically happened in the foreground and prohibited the user from working with Vim while your checkers did more semantic reference loading.

Neomake does nearly the same thing except that it does all of this in the background (again, thanks to job control). This allows you to continue working on the code, or even jump to another buffer, without having Vim be completely frozen while it crunch numbers. This is extremely helpful if you want very precise correction whilst leveraging tools that could get slow over time (like sasslint or gcc).

Bonus: VimStudio

VimStudio is a plugin meant to be used with Neovim so that you can work on Android projects. It’s built with support for neovim but based on code from vim-android and vim-grand. To be honest, I don’t work much on Android projects (or at least, yet) so I haven’t had a chance to work with this plugin. But from glancing at the source, it makes use of the remote plugin architecture of Neovim, which potentially means no blocking calls when working with this plugin.

Neovim is a very interesting project, but as far as I know, it has no officially supported GUI clients. There’s neovim-qt5 but I haven’t built that locally on my machine so I can’t recommend it. What I could recommend though is for you to try out these plugins and the Qt GUI client, see what you think about them and if there’s any quirks you think that’s related to the crafting of the plugin, report an issue on Github. If you’re stuck on how to use the plugin or if it doesn’t work the way you expect, go to StackOverflow. Trust me, loads of maintainers will thank you for not flooding their inbox for things that are in the documentation (if they provide that).

  1. I have to admit, I haven’t the time to look at that issue (I don’t use CMake much anymore). 

  2. Feel like this breaks the rules of some sysadmin guide out there. 

  3. That’s all programming’s about: looping. 

  4. Reminder me to add load testing to cmake.vim. 

Need a hand with tech consulting? I can help!
Learn more about how we can work via black.af .

The ecosystems of the world are dying.
Reduce your :pig::chicken: meat and :cow::goat: dairy intake to help the environment :seedling: .

This site is in the process of moving to Koype. You can view my instance at v2.jacky.wtf.