Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

From VS Code to Helix

ergaster.org

Post reply on HN
Print view View original

101–110 of 142 posts

Re: From VS Code to Helix

#101

Post by dkdcio »

CorrectHorseBat wrote: post #95
dkdcio wrote: post #13

Earlier quoted context omitted.

same -- I wish Helix would just have a full vi-compatible mode, it would probably be enough to get me to switch the other thing for me is lack of the GitHub Copilot extension. I am far too used to having tab-complete. there's some effort for Helix extensions to handle this but it's not close to on-par last time I checked

But why then switch?

from neovim to helix? I would prefer the configuration simplicity (while my neovim config is fairly stable and straightforward, it can be annoying to update) and better out-of-the-box defaults. I’d also be a lot more personally interested in contributing to the Rust codebase of Helix if I ever did run into bugs or features

Re: From VS Code to Helix

#102

Post by gigatexal »

alimbada wrote: post #97
gigatexal wrote: post #53

I’d do the same if they didn’t switch the vim bindings around. All that muscle memory to unlearn. Nope. I went to Zed for this reason.

It's a shame Zed founders unapologetically take money from bigots: https://github.com/zed-industries/zed/discussions/36604

I had thoughts on this but deleted it many times so I dunno really but I guess of all the VCs to take money from... (or maybe this was the only one that would fund a text editor??)

Re: From VS Code to Helix

#103

Post by cycomanic »

airstrike wrote: post #67
dkdcio wrote: post #13

Earlier quoted context omitted.

same -- I wish Helix would just have a full vi-compatible mode, it would probably be enough to get me to switch the other thing for me is lack of the GitHub Copilot extension. I am far too used to having tab-complete. there's some effort for Helix extensions to handle this but it's not close to on-par last time I checked

Ask and you shall receive https://github.com/usagi-flow/evil-helix

I've tried evil helix and it is reasonable close to Vim, but still not quite the same (I don't remember but was running into several slight differences, which were causing enough adjustment that I gave up)

Re: From VS Code to Helix

#104

Post by buzzerbetrayed »

lycopodiopsida wrote: post #16
jsmailes wrote: post #2

Helix 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…

> typing blind on a keyboard I am not used to is anyway a hopeless endeavor.

Sounds like you’re a special case then. Most people can type fine on any qwerty keyboard. And your willingness to turn a blind eye to pretty major annoyances makes it seem like you’re trying to justify the effort you’ve put into Colemak. Even if you aren’t doing that, you’ll get more mileage out of just admitting that it’s annoying to have to use another keyboard.

Re: From VS Code to Helix

#106

Post by timeon »

jsmailes wrote: post #2

Helix 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…

Maybe it is not for people that need to switch. For me it is first editor of this kind and I do not need to fight anything.

Re: From VS Code to Helix

#107

Post by tasuki »

> Helix is a “stupid” text editor. It doesn’t know much about what you’re typing. But it supports Language Servers that implement the Language Server Protocol.

By that measure, isn't eg VS code also a "stupid" editor?

Re: From VS Code to Helix

#109

Post by eviks »

el_memorioso wrote: post #94
eviks wrote: post #72

> Being a lazy person, I never bothered looking up VS Code shortcuts. Because the learning curve for Helix is slightly steeper, you have to learn those shortcuts that make moving around feel so easy. This doesn't make sense: if you were truly lazy, you wouldn't spend any effort learning a more complicated app, you'd simply not switch! > with a few knobs for minor preferences. I am subject to choice paralysis, so maki…

As a long time user of both Emacs (since 18.52) and Neovim and now Helix, I find your last assertion to be false. While it is true that there are many options (though not as many as either Emacs or Neovim), in Helix you cannot write code or install someone else's code to modify your editor. In the past I've spent a good amount of time trying out, integrating, and debugging various packages for Neovim and Emacs. In He…

Just because your current customization needs are primitive in Helix doesn't mean that the potential isn't there!

> might try a new option setting

What about trying to change all the keybinds to suit your emacs/vim needs? What about tweaking hundreds of colors in editor theme?

> in Helix you cannot write code or install someone else's code to modify your editor.

But this is planned, so if only code tickles your fancy, then yeah, you'd have to wait for the full rabbit hole customization potential to appear.

Re: From VS Code to Helix

#110

Post by lycopodiopsida »

buzzerbetrayed wrote: post #104
lycopodiopsida wrote: post #16

Earlier quoted context omitted.

> 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…

> typing blind on a keyboard I am not used to is anyway a hopeless endeavor. Sounds like you’re a special case then. Most people can type fine on any qwerty keyboard. And your willingness to turn a blind eye to pretty major annoyances makes it seem like you’re trying to justify the effort you’ve put into Colemak. Even if you aren’t doing that, you’ll get more mileage out of just admitting that it’s annoying to have t…

> And your willingness to turn a blind eye to pretty major annoyances makes it seem like you’re trying to justify the effort you’ve put into Colemak

Nah, I know vim, meow, emacs keybindings but mostly use boon. I am also able to use my zoo of keyboards in the drawer without any problem, including Model100, KA2 and Glove80. Not everyone is limited by difficulty of learning a skill. There was absolutely no reason to keep qwery and staggered keyboard skills sharp, so I did let it go. Q.E.D.

Post reply on HN