Using Helix - Coming from VSCode (3 weeks in)

I could never get myself set up on Vim, and always ended up on GUI code editors like VSCode. But I've spent the last 3 weeks in Helix using it as my primary editor.

Here is what I love, like and dislike about it.

My config:

My language config:

[kurushimee]

I've been a vim dropout too. I changed back to VSCode after a couple of months trying to use Neovim, because I realized that I can't for the life of mine decide on how I want to config my Neovim setup. I used VSCode instead because it just works without needing to be configured, I was productive with it. With that said, that's part of the reason why I'm loving Helix now: it is fully usable out of the box. More than that, Helix's defaults almost perfectly match my preferences and needs in a code editor, which makes it all the better for me. I like it and I can actually use it because I don't spend all the time configuring it: there isn't really all that much to configure in the first place.

[teprox]

Thank you for your introduction to Helix. ❤❤❤

[D-Oliver]

Nice - thanks for the helpful tips. Regarding hjkl and avoiding moving to the cursor keys, it's definitely worth it. I've been using VIM mode in VS Code for a while now - just the basics - and it's great.

One thing I learned this week is Ctrl+N/P for navigating search results, etc., where j/k isn't an option. That also works in VS code menus. :)

[code-and-optimism]

Thanks Mike! Good video. I like how the fuzzy file-find shows the full path of the files before the file-name. It helps visualize the structure better. I wish VSCode worked the same way! BTW: VSCode has all that multi-cursor goodness. I love that feature.

[SMOKE]

i would have been a Helix user but I am too dependent on vim motions. I do like the way it toggles to select text so when I made my most recent vim config, I added it to it. But now I am using Emacs with evil-mode because Vim wasn't enough, and emacs has a lot of the things available but you just need to enable it and Org-mode (my most favorite thing about emacs). If your up for it, you can use the Doom Emacs distribution. I uses vim keybindings (although some bindings does what it suppose to do but not in the way you expect it. Like when pasting text, in vim, lowercase p pastes text on the same line, I got it to paste on the line below, and Capital p, pastes it on the line above. Emacs copies it where ever the cursor is regardless if its a upper or lower. but besides that, all of the bindings I normally use work as intended.

[SpeculatorSeth]

In the file picker use tab and shift-tab to move up and down the list.

[GodPuck-dwvn]

Thank you so much, your situation was so relatable for me. I was looking for this!
And good joke about light themes, btw.

[defaultgn]

I tried helix and loved it. My only issue is when I need to work outside my editor. Many platforms support vim key binds but not helix bindings

[zayR]

Tried to use helix, liked it, but the lack of snippet support made me go back to neovim for now.

[Primeagen]

Using helix from vscode means: having helix experience in vscode, like vim extension for vim

[marcelo]

You can use lazyvim to make the configuration simpler

[aristotlesimone]

Sublime is a fantastic editor to consider using as well. Its technically modeless, but you can add key bindings to create custom modes if you want a modal experience

[paologaleotti]

You can set helix keybindings to also open commands or apps as a buffer! for example i have C-g to open lazygit. You can do that with yazi

[wken]

man the only thing i really miss is co pilot

[code-island]

whats the point of an editor that as it bests, will looks like neovim?

[such-ej]

It's all cool but can it beat micro? 😄
Helix is pre configured out of the box but if you face any limitation no one can help you (while other editors have multiple extension for any use case). This is a big flaw in a long run.