-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unfriendly Crash #40
Comments
I'm sorry, I haven't touched this project in years and don't have any time to sink into it right now. If you're interested in maintaining it you have my blessings. |
Thanks, I am considering that! Is there much interest in it?
…On April 24, 2018 4:30:23 PM EDT, Mark Probst ***@***.***> wrote:
I'm sorry, I haven't touched this project in years and don't have any
time to sink into it right now. If you're interested in maintaining it
you have my blessings.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#40 (comment)
|
Not that I know. It would be nice if it built and the basics worked, at least, but to make it useful a LOT of work would have to be done. This is barely an out-of-date proof of concept. |
...and yet it's already quite awesome!
Do you have a pointer to notes about the design, what's needed, pet peeved, etc.?
And/or, perhaps we could live-chat about it sometime?
…On April 24, 2018 4:44:46 PM EDT, Mark Probst ***@***.***> wrote:
Not that I know. It would be nice if it built and the basics worked,
at least, but to make it useful a LOT of work would have to be done.
This is barely an out-of-date proof of concept.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#40 (comment)
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
|
I'm happy to chat about it! Shoot me an email at [email protected] |
I tried running a program that expected at least one argument, without providing arguments, and got this:
Seems a little unfriendly. Perhaps there's a reasonable way to avoid this and do something more elegant instead?
Here's the source (it'll look familiar):
The text was updated successfully, but these errors were encountered: