❤️‍🔥 I need this editor alive!

[boozook]

This is a single project in the Universe that

• I love it! 😻
• has native UI
• has no garbage/shit
• has potential and could be moved forward (maintainable)
• almost ready (or close to become ready) for real use
• looks really good
• looks free from "strange vendor's priorities"

I need it really and want to replace such terrible things like vscode and zed (I really have reasons).

And I probably can help with code. I know Swift, but it isn't a main language for me, I mainly writing all in Rust last (ten) years.

---

Another one almost-good-enough editor is Lapce, but Lapce is looking more dead then CodeEdit.

[austincondiff]

@boozook It is still alive! I am glad to see you see in it what we see. I've hit a few personal challenges and will resume development in the next few months when things normalize. You are welcome to dig in and contribute where you can!

[wpostma]

There are basic things like FIND that I would have coded on the first day not coded tho.

#1924

I have had a look through the code and I'm not sure how much of the code exists, if this is a bug (NSFirstResponder stuff) or just something that was NEVER coded. Knowing that would help me figure out how to fix.

This is less ready for real use than any editor I have yet seen. It's more a 0.1, honestly.

I wouldn't mind trying to fix the find feature.

[wpostma]

I had a try, and XCode's terrible swift package system is fighting anyone who wants to both improve a package inside (which wasn't ready for becoming a package, but oh well) the package ecosystem, and also be able to use a local version of a package, and have that in version control, when xcode and swiftpm are fighting y ou.

Lesson learned; Don't make packages of things still in early development.