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.
Which Vim/Emacs/… starter kit sets up the same keyboard navigation model as Helix uses? I think that it’s its main strength, the selection -> action approach, which is quite intuitive (at least for me once I’ve tried) is what really matters in Helix. The rest is just an addition, the one that makes it a quite competent and convenient environment to work with, but an addition.
@fleg @lukas I’m mostly a kakoune user, but when I use emacs for org mode I use meow-mode
Emacs 29 supports tree-sitter out of the box if you’re referring to code navigation. No starter kit uses Helix keybindings yet afaik.
I saw the Helix demo video and that aspect feels like extra steps to me. Perhaps the wiki is poorly worded, but I can select a word, a paragraph, a line, etc. and then delete, change, yank, etc. it in Emacs. Although I also have the option to ignore that approach wherever appropriate. I don’t need visual help to delete the next word, Emacs can do that for me with one keybinding.