helix

Here's one way to see. Look at closed PRs with "changes requested" reviews: https://github.com/helix-editor/helix/pulls?q=is%3Apr+is%3Ac...

Not yet in release branch, afaik https://github.com/helix-editor/helix/issues/401

I keep trying Helix but just got hit by wq freeze issue, opened since 2022, so I wonder sometimes if its ready. https://github.com/helix-editor/helix/issues/2059

Worth mentioning that while this was very nice work by a Helix enthusiast, it was proposed as a replacement for the official docs and mostly rejected, and for good reasons IMO. An instructive discussion! https://github.com/helix-editor/helix/pull/12127#issuecommen... It's rarely a good idea to do a bunch of work on a big change to an open source project in a direction that has not been validated by the maintainers. Or at least, if you do, do it for your own education and don't have high expectations that it will be merged. The contributor in question had a very good attitude about it.

I'm a mostly happy helix user - but I'm still struggling to get debugging to work - both with ruby/rails and typescript/node (Adonis). Apparently DAP protocol support has been merged - but I find the documentation lacking, and afaik for typescript/javascript it won't work out of the box, as helix needs a pointers to the dap server (and that can't simply be in PATH)? How are everyone debugging with Helix? https://github.com/helix-editor/helix/discussions/9269

Helix's features look very cool, but I could not switch to it because of this bug [0]. It has been open since May 2022 and it is still not fixed. Basically you can't exit insert mode with a key combination like `jk`. Four years feels like a long time for such a basic bug. I will stick to NeoVim for now. 0. https://github.com/helix-editor/helix/issues/2612

I've noticed that editors tend to struggle much more with long lines than long files (many lines), even in 2025 with a recent computer. For example, I was recently working with a csv with 50 columns, and each value was a bit long. Things got sluggish at the end of the lines in Helix [0][1][2]. (side note: diffing this kind of files is also a pain, too, but that's another story) It isn't the first time I notice this issue (the first time I tried diffing some minified Javascript with 100k+ long lines). So I guess it might be due to syntax highlighting on top of text encoding [3]. (To partially answer my own question: this performance metric is probably not tested nor optimised for in the first place. And also because not every edit/movement uses async rendering). [0]: https://github.com/helix-editor/helix/issues/4513 [1]: https://github.com

Plugins, coming to a release near you: https://github.com/helix-editor/helix/pull/8675#issuecomment... Or you could check out the branch where the plugin system and the community's plugins have been kicking around for a while now

Annoying, isn't it? I am running a trivial fork to change the `x` behavior on an empty line. https://github.com/helix-editor/helix/pull/4847

Does not work on Linux. Also, double-clicking to expand selection like in Sublime does not work. https://github.com/helix-editor/helix/discussions/10208

I use :reflow (mapped to =) decently well for wrapping comments, but it doesn't do well at splitting a long single line into multiple lines. My workaround is to add a second empty comment underneath and include it in the selection before hitting =. Likely fix here, coming soon according to the last comment: https://github.com/helix-editor/helix/pull/11738

I tried to switch from neovim to helix for a couple weeks, but noted down the following things that were essential to me and not implemented yet: - Code actions on save, for example adding Go imports: https://github.com/helix-editor/helix/pull/6486 - Fuzzy search with a filepicker like telescope+rg, seems to have been added earlier this year: https://github.com/helix-editor/helix/pull/11285 - Automatically updating buffers when the files on disk change (claude, templ, sqlc, etc): https://github.com/helix-editor/helix/issues/1125 - File tree in browser, which has been rejected in favor of a plugin system which has not materialized yet: https://github.com/helix-editor/helix/pull/5768 There were a number of other things too, that I could have lived with. I guess I'll try again in a year or two.

Their cargo.lock file is 3500 lines or so: https://github.com/helix-editor/helix/blob/master/Cargo.lock So, I kind of agree with you, but that’s still a lot of dependencies baked into the editor. It’s probably not as bad as Neovim+plugins, but it’s still a supply chain issue.

There's a fair bit of discussion about this here: https://github.com/helix-editor/helix/discussions/4037 But the short answer is no. Not yet. I'm pretty happy just letting the standalone agent write to the file and then reloading it in my editor. Though I wish the agent CLI tools would use something like inotify to notice when I've made a manual change to a file that they've recently written and then do a better job of incorporating that change as feedback to inform future edits.