Pre-requisites

To use this, you'll need:

• NeoVim (obviously) and
• curl
• Python (+3.6) with pynvim installed

The curl is required to fetch and install vim-plug.

Installing files

To setup the files for NeoVim:

$ git clone git@github.com:lsdr/nvim.git nvim
$ make install

This will do the following:

1. Check for existing configuration files and immediately exit if it finds one
2. Put in place a $HOME/.config dir if it doesn't exist already
3. Symlink this repos to ~/.config/nvim
4. Create needed dirs (plugins, tmp)
5. Install vim-plug
6. Fire nvim to install plugins declared in the configuration files

NeoVim is ready to roll just after the make is done.

Why the Symlink dance?

NeoVim follows the XDG Base Directory Specification, meaning that configuration files will live in the $XDG_CONFIG_HOME which, in turn, is usually set to $HOME/.config.

I don't like to keep code/settings repos spread across my $HOME, so I leave then in ~/Code or something and symlink stuff where applications can find it.

The only project I had that broke this convention was my vim files, but starting fresh with NeoVim is a good opportunity to fix this.

Configuration Files

Configuration files live in the conf.d dir and have a two-digit trailing number to serve as both a visual cue when I'm in a terminal working on them and to make sure files are loaded following a logical order.

Although the latter sounds more important, in the end I care more about the former. So far, there's no need for a ordered loading process to use this setup.

Convention

Digits are used according to the following (very arbitrary) convention:

• 00-29 reserved for significant configuration and custom functions
• 30-59 for programming language setup and tweaking
• 60-89 unused for now
• 90-99 plugins, trackers, tools, fun stuff; everything in this range can be removed and no one would notice

Troubleshooting

• Found an existing $(path to nvim) exiting

  You can clean existing configurations: make clean

🀄