[archseer]

There's this config you might like: https://github.com/LGUG2Z/helix-vim

We can't invert the bindings though (wd -> dw) because that would require a big internal change to add operator pending mode:

When you press `d` in vim, that enters the operator pending mode, where it will wait for an object to be specified, in this case `w` and then delete it.

In a selection first model, `d` is very simple: it just always deletes the selection. So you select a word, then delete.

[e12e]

I tried the "vim" keybindings, but I quickly gave up on it. Helix is a modal editor, but it is not (imnho) a vi/vim-like editor.

It has the potential to be much better at editing code (with a "sense" of the ast) than vi. The trade-off might be that it's slightly more difficult to edit arbitrary/semi-structured text.

I believe (but it's a little early to be sure) that the difference in approach to editing is a net win when working with code.

My advice if coming from vi(m) is to treat helix as a new editing experience - like you would if you were trying out emacs or acme.

The nuanced similarities then to overshadow how helix is different from vim - for better and for worse.