Helix does not aim to be a better vim / neovim. Thus, for example, there are officially no vim bindings and Helix follows the selection → action model. Helix is also a relatively new project.
Helix does not aim to be a better vim / neovim. Thus, for example, there are officially no vim bindings and Helix follows the selection → action model. Helix is also a relatively new project.
When I first tried Helix, my main concern (that prevented me from getting too far into it) was not going from Vim to Helix, but the other way around. Vim (or sometimes vi) is a standard editor on almost any Linux machine, so if I am ever working on a server if a VM, I would need to know/use Vim keybinds. That made Vim a more useful tool for me to learn at the time, as I could use the skills both on my machine and anywhere else.
I don’t feel like this is true anymore. Many distros do not ship vi(m) anymore but only nano.
Seems like most rpm based distro still ship vi/vim and don’t default to nano.
Good to know. In Debian and Gentoo nano is the only editor by default.
I understand the argument, but in my opinion it is used far too often and is not always true.
Not everyone works with servers on which they have no influence on the installed software.
And in the few cases where I had to work with servers on which I had no influence on the installed software and on which actually only vim was installed, I could always use sshfs or rclone mount without any problems so that the editor I used didn’t matter.