Repository navigation
What's going on #16261
Replies: 11 comments 15 replies
|
I'd like to insert my voice here that, if development on helix has stopped completely, the project should be passed on to the community in some fashion so it doesn't die. |
|
helix -> helixc (riff off the KeePassX -> KeePassXC fork?) |
|
neohelix |
|
A post-post-modern modal text editor. |
|
In another thread somewhere someone made the joke: a post-mortem editor :-D |
|
I believe in Helix, please stop all this doom and gloom! It has only been 2 months of no commits, hardly time to fork the project. I am sure the maintainers have their reasons for being away and will return in due course. I know it is frustrating that they won't comment, maybe there is some personal stuff going on, they don't owe an explanation. |
|
I hope things pick up. In the meantime, I have mattwparas steel fork built, rainbow brackets enabled, and I am very happy |
Over a year since the last release... I mean I also believe in the project and Helix has been my main driving editor for a couple of years now and I am forever grateful to the maintainers for that, but all I'd ask is at least some sort of communication. |
|
Rainbow brackets are already in the master, you don't need a for it :) |
Yes! I’ve been using them this last week since I discovered that. I just needed the file watcher reloading on top of that |
|
I'm all for a soft fork. By soft fork, I mean, that it should always be able to easily diff and squash it back to proper Helix when it becomes active again. |
|
But when (if) the maintainers get back at the project we will have two competing helices (😅) that would diverge. |
|
That sounds like fun. Do it for the memes |
|
Therefore we really need a statement of the status quo from the maintainers. |
|
Do it for the memes. |
|
Some of you may be interested by this: https://github.com/mitos-editor/mitos |
|
looks good, has even breadcumbs support, long awaited feature in helix it has even its own webpage, looks like a serious fork |
|
New commits have started popping up, the project is alive |
|
The project is alive! Big ups to maintainers! |
|
I am happy to see those latest commits. I would be even happier, if we could have a statement if regular development (and releases) will recommence or if a community fork is the way to go. |
|
how do you feel as a meatproxy? |
|
I just want to help 🤡 |
|
How do I even respond to that Edit: https://nomeatproxy.com/ |
|
Project seemingly went back to sleep again, so I finally caved and switched over to the steel plugin fork last night and build everything from source although that's the last thing I wanted to do. |
|
As I already stated in the other thread: #15733 I don’t really care about „major“ new features. All I expect is that the maintainers are doing their homework: bug fixes, polishing, and here & there some small QoL enhancements. Built with the latest compiler and released approx. twice a year. And until July ‘25 that’s how it worked… |
Uh oh!
There was an error while loading. Please reload this page.
Can the maintainers please comment on the state of this project and provide a REALISTIC timeline on when the next release is expected, or if the project is dead? People have been asking over and over what the plan is, and there are scores of PR's done by contributors that are just sitting in limbo. Last I heard the release was set for February/March 2026?
I get the project is open source and you have jobs, but its not hard to write a short, honest answer for the people that support your work rather than passive aggressive hand waving every time someone asks.
I would be happy to start a fork/contribute to someone else's fork if the maintainers are no longer interested in regular maintenance, but I wanted to open the discussion first.
All reactions