- 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.
I’ve been trying helix and the built in LSP integration is excellent. Out of the box it’s capable of a lot when paired up with a good language server. The equivalent LSP integration on neovim takes some fat plugins.
I will say helix seems immature in a few areas. I noticed it’s missing tab layouts present in vim. Also might it not be impossible to resize splits? There’s also no linewise selection mode.
Helix out of the boz is close to my 15 years of accumulated vim config, but it seems like it’s not quite there yet.
I always found the tab bar in vim to be confusing. Does not out the box do what other editors use it for. So I am glad that it is missing from helix in that form. As for a tab bar that other editors use, well I guess vim already beat into me the need to not really use one. I do find that I don’t really miss it with all the ways to open files and select buffers in helix
<space>bfor instance to see and fuzzy search buffers is very nice (or<space>ffor all files).Not yet it seems, though #1176 is tracking that and looks like someone implemented it a while ago. Might want to add your view to that issue to raise its importance.
Xwill extend the selection to full lines andxwill also advance the selection by one line. I don’t think there will ever be a separate linewise selection mode due to how helix treats new lines. Though these keys are good enough for most situations.