I switched after development ended on the package manager I was using on neovim. I didn’t at that moment want to simplify my vimconfig, so I looked into helix.
Helix highlights the action you take, so if for example, you are deleting 5 lines, you select the lines first then hit delete. Sometimes the vim actions end up taking fewer keystrokes though. And I still prefer some ways vim does things. And I don’t always agree with the kakoune inspiration of helix (I haven’t used kakoune, just going by what the docs say) - for example, movement always selects text which I then have to unhighlight.
But the biggest reason I stuck to helix was sane LSP defaults out of the box with minimal config. I was tired of having to fix LSP related bugs in my vim config after package updates.
TLDR: saner defaults for helix + lazy to fix my bloated vimconfig.
i have sort of done this. the main thing is that the reversed object-verb command model just… latches onto your brain. this is from kakoune of course, but it just makes a lot of sense coming from vimland. multicursor is also nice because it removes some modes, meaning there is less state to keep in your head. finally, the plug-and-play nature of helix means you can have an lsp-enabled environment from the word go, with no configuration.
Personally, I love to tinker (especially on my main machine) so I don’t mind the complexities of setting up neovim. However, I do mess around with a bunch of servers, and I like to edit code on those servers, meaning I am often installing/compiling neovim and copying over my config before I can get to work.
What I am liking about helix is the idea that its default setup has what I need to get started straight away.
Just out of interest, what are the reasons someone would move from neovim to helix?
I switched after development ended on the package manager I was using on neovim. I didn’t at that moment want to simplify my vimconfig, so I looked into helix.
Helix highlights the action you take, so if for example, you are deleting 5 lines, you select the lines first then hit delete. Sometimes the vim actions end up taking fewer keystrokes though. And I still prefer some ways vim does things. And I don’t always agree with the kakoune inspiration of helix (I haven’t used kakoune, just going by what the docs say) - for example, movement always selects text which I then have to unhighlight.
But the biggest reason I stuck to helix was sane LSP defaults out of the box with minimal config. I was tired of having to fix LSP related bugs in my vim config after package updates.
TLDR: saner defaults for helix + lazy to fix my bloated vimconfig.
i have sort of done this. the main thing is that the reversed object-verb command model just… latches onto your brain. this is from kakoune of course, but it just makes a lot of sense coming from vimland. multicursor is also nice because it removes some modes, meaning there is less state to keep in your head. finally, the plug-and-play nature of helix means you can have an lsp-enabled environment from the word go, with no configuration.
That’s a good enough excuse for me to try it! Thanks.
deleted by creator
Personally, I love to tinker (especially on my main machine) so I don’t mind the complexities of setting up neovim. However, I do mess around with a bunch of servers, and I like to edit code on those servers, meaning I am often installing/compiling neovim and copying over my config before I can get to work.
What I am liking about helix is the idea that its default setup has what I need to get started straight away.
I am looking forward to giving helix a go.
deleted by creator