First time hearing about the Helix editor, and I gotta say — it really caught my eye. I’m not super familiar with Vim, but I’m definitely gonna install Helix and give it a try.
From VS Code to Helix
31–40 of 142 posts
Re: From VS Code to Helix
#32Helix and other new editors (kakoune comes to mind) always appealed to me because they seemed to have slightly more intuitive approaches to editing than vim, but I just don't think I can ever switch, purely because vim just exists everywhere I need it. It (or vi) is installed on practically every system I ever touch by default, and almost every IDE/editor under the sun supports vim keybinds either natively or via wel…
> I'm sure I could learn to be slightly faster on dvorak/colemak, but nothing beats the convenience of always having guaranteed access to qwerty, everywhere I go. Colemak/Dvorak is not about speed, but about comfort and avoiding RSI (though I would place the actual layout somewhere far down on the list, a proper ergonomic KB is top priority). Also, in my ~8 years on Colemak lack of access to it was a problem exactly…
And regarding availability, Colemak is now included in Windows 11, which makes it available out of the box in all 3 major OS's. Also, Colemak is an easy way to upgrade comfort in cases where you can't change the keyboard, like a laptop or shared computer.
Re: From VS Code to Helix
#33Helix and other new editors (kakoune comes to mind) always appealed to me because they seemed to have slightly more intuitive approaches to editing than vim, but I just don't think I can ever switch, purely because vim just exists everywhere I need it. It (or vi) is installed on practically every system I ever touch by default, and almost every IDE/editor under the sun supports vim keybinds either natively or via wel…
> I'm sure I could learn to be slightly faster on dvorak/colemak, but nothing beats the convenience of always having guaranteed access to qwerty, everywhere I go.
Citation needed. Of my 2 friends that have tried, neither have been able to reach their 'standard' typing speed after 1+ years of dvorak. Maybe they didn't try hard enough?
Re: From VS Code to Helix
#34The best part of this article for me is the link to these well made 3rd party docs for helix.
https://helix-nikita-revencos-projects.vercel.app/start-here...
Re: From VS Code to Helix
#35Helix's features look very cool, but I could not switch to it because of this bug [0]. It has been open since May 2022 and it is still not fixed. Basically you can't exit insert mode with a key combination like `jk`. Four years feels like a long time for such a basic bug. I will stick to NeoVim for now.
Re: From VS Code to Helix
#36Helix boast itself as a no config tool, but you have to find a lsp, installl it, edit a toml to activate it. I dont think we can call that "config less". Success would be something like LazyVim but without the nagging of updates each time you open it.
I am whole off the vim (&friends) trend but my 2c-
The helix situation is still miles better for up and running asap compared to dancing with files/lua on lazyvim. Just having to refer to docs to install a plugin, writing sane remaps etc eats up time. If you really just speedrun everything under an hour good for you. But for the rest, a lsp is a one package manager install away (even on windows scoop seems to have become the de facto), editing a toml is much easier than fiddling with the lua api/vimscript "just" to set some variables.
(Not a helix user though I have tried both vim/nvim/helix)
The only problem for me was the keybindings work good unless my vim instincts kick in where I become slow. The other one was lack of plugins.
Re: From VS Code to Helix
#37Helix and other new editors (kakoune comes to mind) always appealed to me because they seemed to have slightly more intuitive approaches to editing than vim, but I just don't think I can ever switch, purely because vim just exists everywhere I need it. It (or vi) is installed on practically every system I ever touch by default, and almost every IDE/editor under the sun supports vim keybinds either natively or via wel…
> I'm sure I could learn to be slightly faster on dvorak/colemak, but nothing beats the convenience of always having guaranteed access to qwerty, everywhere I go. Colemak/Dvorak is not about speed, but about comfort and avoiding RSI (though I would place the actual layout somewhere far down on the list, a proper ergonomic KB is top priority). Also, in my ~8 years on Colemak lack of access to it was a problem exactly…
> avoiding RSI
I tried all manner of keyboards over the years, and in my opinion, none of them solve RSI. I'm now back to a standard qwerty for the same reason as OP - they're just immediately available everywhere.
What did help my no-longer-existent RSI was simple - I don't rest my wrists any more like I was taught in high school typing class (by an instructor that would whack our hands with a ruler if we were caught resting our wrists).
I do have a bit of De Quervain's Tenosynovitis from the mouse, but I'm solving that with one of those hand stretchers that hook to your fingers and provide resistance when opening the hand. 100 reps a day (25x4) and I haven't really felt it in weeks. Turns out that working out the muscles opposite to the ones you think is the key (therapy putty did nothing).
Re: From VS Code to Helix
#38Helix has its limitations — but I use it for speed. No other editor I’ve tried is as nimble.
Re: From VS Code to Helix
#39Helix and other new editors (kakoune comes to mind) always appealed to me because they seemed to have slightly more intuitive approaches to editing than vim, but I just don't think I can ever switch, purely because vim just exists everywhere I need it. It (or vi) is installed on practically every system I ever touch by default, and almost every IDE/editor under the sun supports vim keybinds either natively or via wel…
[deleted]
Re: From VS Code to Helix
#40Last i checked helix did not have a way to run commands and pipe results to something like quickfix. Is this a thing these days?