My hope is that Helix gets around making /**/-style block comments more ergonomic. It's one of the reasons I'm still using nvim for writing C.
Helix 23.10 Highlights
31–40 of 76 posts
Re: Helix 23.10 Highlights
#32Release size is ridiculous, and they refuse to do anything about it https://github.com/helix-editor/helix/issues/6187
I can understand complaining about RAM usage because there is some performance impact there, but I have truly no clue why anyone cares about storage usage.
Other than the initial download time, I don't see how it would have any impact on the end-user.
Of course, it would be _nice_ to get that package size down if it's easy, but to me it seems unnecessary to prioritize.
Re: Helix 23.10 Highlights
#33Re: Helix 23.10 Highlights
#34Earlier quoted context omitted.
$ du -hs /opt/homebrew/Cellar/helix/ 139M /opt/homebrew/Cellar/helix/ That doesn't seem unreasonable to me.
is helix built on electron?
> Built in Rust, for the terminal
> No Electron. No VimScript. No JavaScript. Use it over ssh, tmux, or a plain terminal. Your laptop battery life will thank you.
Re: Helix 23.10 Highlights
#35I've been using Helix full time, professionally as a Rust/Golang engineer and it has been great. It took some getting used to not having a file explorer. But now I think I am better for it. These looks to be fantastic updates, I especially dig the diagnostics (if that is part of the release as well).
what's your workflow like for situations where you need to poke around in an unfamiliar directory and open files in helix?
The only thing I haven't nailed yet is creating files in deeply nested directories.
In general most of the things I used in nvim have now moved back to the terminal which has its pros and cons.
Re: Helix 23.10 Highlights
#36I've been using Helix full time, professionally as a Rust/Golang engineer and it has been great. It took some getting used to not having a file explorer. But now I think I am better for it. These looks to be fantastic updates, I especially dig the diagnostics (if that is part of the release as well).
what's your workflow like for situations where you need to poke around in an unfamiliar directory and open files in helix?
Re: Helix 23.10 Highlights
#37I've been using Helix full time, professionally as a Rust/Golang engineer and it has been great. It took some getting used to not having a file explorer. But now I think I am better for it. These looks to be fantastic updates, I especially dig the diagnostics (if that is part of the release as well).
I also use Helix full time, I really like it, especially the multi cursor features. I was a neovim user before, but I did not enjoy configuring my editor all the time. I like Helix config defaults, LSP works out of the box, the commands are a bit longer to type, but more logical. I cannot work without a file tree, I settled with the tree explorer fork[1] and I'm happy with it. [1] https://github.com/helix-editor/heli…
Re: Helix 23.10 Highlights
#38Never could stick to any modal editor like (neo)vi(m), but helix was so easy to get into, and you don't even need to configure anything.
My main editor and "IDE" since >1 year, can only recommend.
Re: Helix 23.10 Highlights
#39Smart tab is so… smart. I really admire how people keep coming up with creative features that immediately make sense and become table stakes right away. This applies to editors across the board. Couldn’t imagine living without command palette in VSCode, for example. Smart tab looks like something I’d be using constantly. Does anyone have experience switching from VSCode to Helix? I’m using a ton of different features…