Transitioning from Neovim to Helix Editor for Remote Development
By
f311a
7mo ago· 4 min readen
65/100
Toasty
Bagelometer↗
Lightly toasted, lightly seasoned, mostly correct.
Score65Typehow-toSentimentpositive
Summary
The author shares their experience switching from Neovim to Helix editor for remote server development, highlighting the motivation to avoid plugin-heavy setups due to supply-chain security concerns. They discuss their configuration approach, including tmux integration and workarounds for missing features like file managers and git TUI. The article provides practical tips for making the transition from Neovim to Helix smoother.
Key quotes
· 4 pulledI've been using Helix as my editor to develop on remote servers for quite some time now.
There are a lot of emerging supply-chain attacks, and I simply don't like the idea of installing tens of plugins to Vim/Neovim to make the editor usable.
To make the switch from Neovim easier, I had to make some changes to the configuration. I want to share them to save you some time, because discovering them is not straightforward.
One thing that I miss from Neovim setup is a good file manager and TUI for git.
My Helix editor config and how I'm using it
