Portable Neovim and Docker shenanigans

How would you like to port your Neovim between different platforms and machines using a single token and command while knowing exactly how it will behave?

Most of my Docker containers have been running services using compose instead of being temporary execution environments.

Trying out Helix in an earlier article inspired me to containerize my Neovim setup. During this process, I learned a lot and had some aha moments.

This a continuation to my last article about Helix.

Being inspired, but I still came back

My brief run with Helix is coming to an end for now. After using Helix for around two weeks I started having an urge to bring my Neovim config up to speed instead of launching Helix.

What I gained from trying Helix was some much-needed perspective and joy to delve into my Neovim configuration. Instead of making large changes, I mostly went through my config again trying to discover things that I had missed or forgotten about.

Investigation time

Helix has been on my mind for a long time, but I never got around to it. It is time to fix that.

I’m doing this comparison between Helix and Neovim, which has been my editor of choice for a long time.

This document is WIP, so it might not be completely factually correct. I’m writing this while learning.

Should you?

Yes, even if you are a hardcore Vimmer I think you should try Helix.