Live data from Hacker News

Helix: A Neovim inspired editor, written in Rust

github.com

301–310 of 321 posts

Re: Helix: A Neovim inspired editor, written in Rust

#301

Helix author here: I think the poster chose an unfortunate headline. 1) Helix was written to replace my neovim setup but is in fact kakoune inspired. 2) It's written in Rust but I don't draw focus to it precisely because RiiR/"X in Rust" posts are getting a bit tiring to see.

Helix is awesome. Thank you for doing this!

Re: Helix: A Neovim inspired editor, written in Rust

#302
post #10

I fully expect Helix to replace Vim, Neovim, and Kakoune for most users in the long run. Helix is built from the ground up around Tree-Sitter and LSP. This means you get the best syntax highlighting available, and IDE-like functionality, with zero configuration required other than installing the appropriate language server. Those are by far the most important features for a text editor to have, and crucially, they ar…

I fully expect Helix to replace Vim, Neovim, and Kakoune for most users in the long run. Yeah, that’s not going to happen. It’s cool to have choices, but you wouldn’t be the first person to think a new editor is going to replace Vim/Neovim. Vim is literally on every Unix/Linux server; every sysadmin can count on it being there. I’ve been super impressed with the progress of Neovim and the team behind it. It’s only at…

> every sysadmin can count on it being there.

Ah, this old chestnut.

I don't disagree with your overall point, but that audience is pretty small, and the number of people who text edit a lot that a) need to float between machines frequently AND b) don't have enough access to install what they want is even smaller.

Re: Helix: A Neovim inspired editor, written in Rust

#303
post #10

I fully expect Helix to replace Vim, Neovim, and Kakoune for most users in the long run. Helix is built from the ground up around Tree-Sitter and LSP. This means you get the best syntax highlighting available, and IDE-like functionality, with zero configuration required other than installing the appropriate language server. Those are by far the most important features for a text editor to have, and crucially, they ar…

I fully expect Helix to replace Vim, Neovim, and Kakoune for most users in the long run. Yeah, that’s not going to happen. It’s cool to have choices, but you wouldn’t be the first person to think a new editor is going to replace Vim/Neovim. Vim is literally on every Unix/Linux server; every sysadmin can count on it being there. I’ve been super impressed with the progress of Neovim and the team behind it. It’s only at…

but you wouldn’t be the first person to think a new editor is going to replace Vim/Neovim. Vim is literally on every Unix/Linux server; every sysadmin can count on it being there.

Even that is a new(ish) development. For a long time people where saying exactly that about vim. I'm not _that_ old, and I was told early in my career not to get too dependent on either vim or the GNU tools since they probably won't be installed on most systems you connect to.

Re: Helix: A Neovim inspired editor, written in Rust

#304
post #201

Earlier quoted context omitted.

You can also use `gh` and `gl` for start and end of line (and `gs` for first non-whitespace character in line). These options (among others) pop up when using helix and typing `g`.

Ok, so in vim I'd type 'd$' as "delete to end of line". What is the equivalent in helix? EDIT: while I'm here, where are the sentence and paragraph movements?

In Vim, you can also type `D` to save a keystroke.

Re: Helix: A Neovim inspired editor, written in Rust

#305

Earlier quoted context omitted.

>I've used Helix for all my recreational programming projects (in Rust) for about 6 months and I've written about 10kLOC of code with it. Still using vim at $WORK for a variety of reasons (giant c++ codebase that does not easily plug in to clangd/LSP), but I might be doing the switch soon. Do you have some supernatural ability to quickly (re)learn muscle memory for new keybindings? I’d consider myself a fairly advanc…

After 20 years of vim I decided to try out Helix back in Feb and never looked back, so I guess I can chime in here. Sure, it took a few days (maybe weeks?) of feeling uncomfortable, but unlike vim, Helix is very approachable. I think you have to be okay with a certain level of feeling uncomfortable if you want to do or learn anything new though. If learning a new editor isn't your thing, then don't. :) I get this sam…

Slightly off-topic: how do you manage using an alternative layout with an editor like vim/Helix? I've been trying to figure out how/if to remap the keys in the editor condig.

If you remap hjkl to your right-hand home row, that could cause a cascade of other remappings. If you don't, you lose basic navigation with hjkl.

Re: Helix: A Neovim inspired editor, written in Rust

#306
post #16
post #10

I fully expect Helix to replace Vim, Neovim, and Kakoune for most users in the long run. Helix is built from the ground up around Tree-Sitter and LSP. This means you get the best syntax highlighting available, and IDE-like functionality, with zero configuration required other than installing the appropriate language server. Those are by far the most important features for a text editor to have, and crucially, they ar…

> Helix is built from the ground up around Tree-Sitter and LSP. Sadly, that achievement is compromised by having to call into unsafe code.

as opposed to c or c++ which is effectively unsafe EVERYWHERE?

Re: Helix: A Neovim inspired editor, written in Rust

#307

Earlier quoted context omitted.

After 20 years of vim I decided to try out Helix back in Feb and never looked back, so I guess I can chime in here. Sure, it took a few days (maybe weeks?) of feeling uncomfortable, but unlike vim, Helix is very approachable. I think you have to be okay with a certain level of feeling uncomfortable if you want to do or learn anything new though. If learning a new editor isn't your thing, then don't. :) I get this sam…

Slightly off-topic: how do you manage using an alternative layout with an editor like vim/Helix? I've been trying to figure out how/if to remap the keys in the editor condig. If you remap hjkl to your right-hand home row, that could cause a cascade of other remappings. If you don't, you lose basic navigation with hjkl.

I use Dvorak, although I regret the choice to learn it instead of Qwerty. If you don’t remap, and I don’t, then you need to use two hands instead of one to navigate. Not a dealbreaker for me though, since by coincidence the places hjkl ended up on Dvorak that makes navigating with them tolerable.

Re: Helix: A Neovim inspired editor, written in Rust

#308
post #268
post #255

Earlier quoted context omitted.

VSCode has a vertical 'subwindow' on the left which list all the opened tabs. I call this 'a tab view/list', I don't know what's the real name. Usually I have between 10 and 20 tab opened, so the tablist is very helpful for navigating between tabs. Unfortunately (AFAIK) the 'fast' editors (vim, kakoune, etc) don't provide such feature. Some have a tree list but not a tab list :-(

Built something like this a few years ago: https://github.com/roblillack/vim-bufferlist

Thanks a lot, I don't know why I haven't been able to find it..

Re: Helix: A Neovim inspired editor, written in Rust

#309
post #276
post #255

Earlier quoted context omitted.

VSCode has a vertical 'subwindow' on the left which list all the opened tabs. I call this 'a tab view/list', I don't know what's the real name. Usually I have between 10 and 20 tab opened, so the tablist is very helpful for navigating between tabs. Unfortunately (AFAIK) the 'fast' editors (vim, kakoune, etc) don't provide such feature. Some have a tree list but not a tab list :-(

In vim, you can list open buffers with :b Edit: sorry, it’s actually :ls

Sure, but I wanted to have an "always opened" subwindow like da_rob has implemented. I wonder why I haven't been able to find it before, I've tried!

Re: Helix: A Neovim inspired editor, written in Rust

#310

Earlier quoted context omitted.

Slightly off-topic: how do you manage using an alternative layout with an editor like vim/Helix? I've been trying to figure out how/if to remap the keys in the editor condig. If you remap hjkl to your right-hand home row, that could cause a cascade of other remappings. If you don't, you lose basic navigation with hjkl.

I use Dvorak, although I regret the choice to learn it instead of Qwerty. If you don’t remap, and I don’t, then you need to use two hands instead of one to navigate. Not a dealbreaker for me though, since by coincidence the places hjkl ended up on Dvorak that makes navigating with them tolerable.

Instead of qwerty?? Never even considered that a possibility.

I also don't remap anything. It's fiiine. You'll get used to it :-)

Post reply on HN