(no title)
kirillbobyrev | 3 years ago
The subtle differences are both good (many things out of Vim work out of the box in Helix) and painful (the ones that don’t give an awkward feeling.
Awkward take on that is that I think if Helix came up a completely different key bindings it would be easier to switch to…
Edit: the differences are not way too dramatic but slightly annoying since many of those are very frequent actions - https://github.com/helix-editor/helix/wiki/Migrating-from-Vi...
e12e|3 years ago
I'm still trying to use helix, as I think the design of the keyboard interaction is mostly an improvement on vi/vim. I think there are some shortcuts that helix stil need to "figure out" - like vim dd, for example (you can delete a line in helix, but you need something like xd. And xx won't work (because it "means" select line, expand to select next line).
And while one could of course remap helix, that would go against most of the benefits of changing imnho. In that case neovim would be more pragmatic.
My biggest pain point / muscle error from vim has turned out to be using x for delete - which surprised me a lot - if you'd asked me I'd probably said I delete with d in some combination or other. Apparently not.
The biggest benefit I see is the synergy between object/subject/selection -> action (wORD cHANGE) and the context menu on space (eg: x (select line) space (context menu) y (yank to system clipboard). It feels about as light as vim "leader", and really helps discovery.
Still not 100% sure I'll stick with it - but I definitely think helix have made a lot of good decisions.
djaouen|3 years ago
kirillbobyrev|3 years ago
Maybe my biggest point is the difference in Vim integrations in IDEs vs using Helix outside of that, so not sure if I should switch but maybe I'm just being too lazy.
blumomo|3 years ago