CodeEdit
Replies: 5 comments 3 replies
|
@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! |
|
There are basic things like FIND that I would have coded on the first day not coded tho. 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. |
|
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. |
|
buying what? |
|
I'm sorry my mistake, this wasn't the correct repo |
|
@austincondiff What's the status of project? Is it still in active development? |
|
No commits in six months. Basics like edit > find incomplete. This is a dead project |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
This is a single project in the Universe that
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.
All reactions