- cross-posted to:
- text_editors@programming.dev
- cross-posted to:
- text_editors@programming.dev
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.
deleted by creator
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
deleted by creator
Starter kits for vim/emacs IMO are a band-aid on the fundamental problem with them - poor default settings for the majority of use cases. I do think that an editor that takes the out the box experience is sorely needed in the cli editor space that helix fills quite nicely.
The big problems with starter kits is they are more fiddly to install - often require you to
curl | bash
some random script. They tend to mess around with your users config files in ways that you don’t always expect. And they require you to keep up to date a large amount of plugins that sometimes end up breaking for various reasons. All of this adds some friction to new users.Yes less friction than creating the configs and fetching the plugins yourself as you need to in vim/emacs. But helix remove all that fiction by just including all people expect from a modern editor from the start.
So I think it does a disservice to discount it completely just because starter kits can do a similar thing after you manage to get them installed.
I am not sure what you mean by this?