Earlier quoted context omitted.
>>And there are several Neovim distributions (LunarVim, Nvchad, etc.) that have all of the bells and whistles included. Problem with distributions is as the contributions decrease they start becoming abandonware with time. Leaving you with with vim and having to work through the configuration hell on the long term for yourself. >>Again, Neovim gives you choices: you can configure and tweak it to your heart’s content…
I agree with this. I spend most of my days on newly created systems (AWS EC2 instances) that are bone stock. I don't use any vim plugins at all because they wouldn't be the same everywhere and it's not worth configuring a system I'll only use for 2 hours. If I could get a full featured IDE installed by default on my systems I would ditch vim in a heartbeat.
Helix: A Neovim inspired editor, written in Rust
311–320 of 321 posts
Re: Helix: A Neovim inspired editor, written in Rust
#312Earlier quoted context omitted.
Right, except for libraries or language-specific toolchain, the only legitimate reason to mention language in the title is to suggest doubt it was possible.
Hey ncmncm, I know this is off-topic, but I just wanted to say that I really enjoyed your informative comments on high performance low-latency architectures. I was wondering, could I ask you a question via email?
Re: Helix: A Neovim inspired editor, written in Rust
#313I 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. I feel like I am definitely not in the "most users" group here. > syntax highlighting ... IDE-like functionality > Those are by far the most important features for a text editor to have. The most important features for me are the ability to navigate around and manipulate whatever's in the buffer(s) efficiently. I'm a 30 year vi…
Re: Helix: A Neovim inspired editor, written in Rust
#314I love to see that Helix tries its best to ensure an out-of-the-box experience, as well as to add so many interactive hints for key combinations (for example when you want to paste in insert mode with C-R it’ll immediately list a set of registers that you can paste from). However Vim is much more to me. It’s not just an editor, but a keybinding that I can use not only in nain, but also in VSCode, in fish shell, and e…
Re: Helix: A Neovim inspired editor, written in Rust
#315Earlier quoted context omitted.
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.
EDIT: Oops, you weren't replying to my 'dd' question. Sorry ignore me. Though if you know the equivalent of 'dd' in helix I'd like to know...
Re: Helix: A Neovim inspired editor, written in Rust
#316Earlier quoted context omitted.
Hey ncmncm, I know this is off-topic, but I just wanted to say that I really enjoyed your informative comments on high performance low-latency architectures. I was wondering, could I ask you a question via email?
Sure, what's your address?
Thanks!
Re: Helix: A Neovim inspired editor, written in Rust
#317Re: Helix: A Neovim inspired editor, written in Rust
#318Re: Helix: A Neovim inspired editor, written in Rust
#319Earlier 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…
I’ve got the same question. One of the major reasons I invest time into vim is because it’s everywhere and so powerful. If I invested time into learning a different set of keys for an editor that isn’t always available, I wouldn’t be able to leverage that power and fluency all the time, and furthermore, would need to switch back and forth between vim and helix keys
Re: Helix: A Neovim inspired editor, written in Rust
#320Earlier quoted context omitted.
I think you're overestimating the likelihood that Tree-sitter is going to gain enough traction to be reliable for general purpose text editing. It's great for popular modern languages, but not for everything, and there's no fallback in Helix. I'm not convinced that's ever going to change.
Reliable? I trust Tree-Sitter's grammars a hundred times more than the underspecified regex monstrosities that power highlighting in other editors. Tree-Sitter grammars are unit tested, have usable primitives for precedence and associativity, and are generally far more predictable than previous highlighting systems. Also, name a language for which there is no Tree-Sitter grammar yet. The only remaining ones are so ob…