Mark StosbergMay 9, 2024

This is why I'm ready to try #HelixEditor after being a long-time #neovim user. This kind of experience is not uncommon when trying to start NeoVim after OS updates, due to plugin complexity.

Helix, so far, doesn't have a plugin system. It likely will eventually but it takes a "batteries included" approach so that enough is included that it's possible to have a good experience without plugins, eliminating this class of complex ecosystem pain.

Show threadGertMay 11, 2024
@markstos This was the exact reason I tried #HelixEditor.
No plugins to keep up to date, no plugings that could break at any point when updating. No endless tweaking of my config so I could get the darned plugins to work properly.
Then learned to use Helix properly and got convinced "selection->action" is the way to go.
Removed neovim everywhere. On servers I'll use a base vim in a pinch. Everything else is Helix.
Go for it, you won't regret it.
Show threadMark StosbergMay 11, 2024

@Gert Until Helix has plugins, this concept for integrating Helix more closely with the terminal looks promising.

It demonstrates a way of integrating "git blame", better git support and live grepping.

https://github.com/quantonganh/helix-wezterm

Though I immediately found a bug in the path handling and have submitted a PR for that.

#HelixEditor

GitHub - quantonganh/helix-wezterm: Turning Helix into an IDE with the help of WezTerm and CLI tools

Turning Helix into an IDE with the help of WezTerm and CLI tools - quantonganh/helix-wezterm

GitHub
Show threadMo Bitar 
@markstos @Gert I don't get this. Why not just use Zellij?
May 11, 2024 at 3:23pmWeb