Installing

Clone this repo into ~/.config/nvim and simply launch neovim. The first time around, it will install all the plugins specified using lazy.nvim.

Plugins

Plugins are managed using lazy.nvim. An interesting features is the config specification, which allows to run code after the plugin has been loaded. This is where I put any plugin related configurations. Hence the plugins and their configurations reside in one single place.

Initially, plugins were managed using packer.nvim but there were some issues — very highly annoying ones — so I decided to switch teams and try out lazy.nvim.

• I had an autocommand which runs :PackerCompile whenever the plugin file(s) is/are saved. Saving 3 times in a row always caused an error. Closing and re-opening vim made it work again. But it would always error out after 3 consecutive saves for some reason.
• Since I split my plugin configurations into different files, the :PackerCompile did not properly catch on and reflect the changes I made to individual plugin configuration files. For it to actually work I had to
  1. :PackerCompile the separate plugin file
  2. :PackerCompile the main plugins.lua file
  3. Restart NeoVim
  4. Run :PackerCompile again on the plugins.lua file
  5. Restart NeoVim
  6. Check if the changes took effect (i.e. :PackerStatus or executing a mapping or whatever else could manifest the modification I made)
  7. If it still did not work, repeat steps 3-6 until it works.

Cool things in my config

Quickly edit config files

Navigation

Windows

Use ALT+{hjkl} to nagivate the open windows. Works from normal, insert and terminal mode!

Tabs

Use ALT+{,.} to cycle through the tabs. Works from normal, insert and terminal mode!

Insert mode

Use ALT+{hjkl} to move the cursor in insert mode. Useful for small movements or if you are too lazy to go to normal mode.

Headers

Lilypond

About this repository

Actually, I already have a .vim config built, expanded and tinkered on for 5 years (Looking at the commit history on GitHub, the first commit was Aug 13, 2017 and the last one was Aug 28, 2022). Given how long this config has been with me, I was always extremely hesitant to make he jump to Lua; especially in light of the the many tweaks, mappings and functions that I wrote over the years.

I rarely use Vim anymore — these days I'm only using NeoVim. Also, if I need to work on a remote server that does not have NeoVim installed, it seems to ship as an AppImage as well. So technically speaking nothing was holding me back.

The thing that pushed me to finally do the switch is that my original Vim config is extremely bloated with a ton of things I practically never use anymore (which counts ultra specific mappings and functions and commands and whatnot). I did put everything accordingly into ftplugin files to avoid it all being a mess, but somehow things felt wonky lately. So I thought a fresh start might do good afterall.

It almost feels like I am betraying Vim by leaving VimScript for Lua, but packer.nvim quickly convinced me otherwise.It is quite a bliss actually to rewrite my config in Lua — or at least those parts that I still need. 😛