Replies: 4 comments 7 replies
|
Sure, good idea. Do we need this to be configurable? Or just change the behavior for everybody? |
1 reply
|
I think I can implement it. I am also leaning towards default with no preferences settings. Barring unforeseen complications, you can expect it in a few days. |
0 replies
|
This is tracked in #244 |
5 replies
|
Version 0.8.3 is released with this update. Thanks for the suggestion. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I typically see command line utilities throw a "unknown command" error and exit when a user tries to call a command that doesnt exist. Currently bashly will just show the usage command instead. Is there any plans to allow an error to be thrown instead or is there a way to accomplish this with Bashly's current features?
So for example
my-cli unknown-cmdwould display an error:Unknown command: "unknown-cmd"and then exit.All reactions