You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Firstly — thank you v much for rargs! I use it a lot. It's probably the most underrated "new cli tools" library.
What should the exit code of an rargs command?
Currently it seems to return successfully even if there were lots of errors in the individual commands.
I'd like to be able to understand if any command failed (e.g. did any string fail to be grepped in a file). Is there a way of doing that with the current library?
The text was updated successfully, but these errors were encountered:
A cursory overview of the code indicates that presently, the only cause for a nonzero exit code is an I/O error trying to read stdin.
(Changing the code to add propagation of childrens' nonzero exit codes, would require some care in order to preserve the potentially-desirable behavior that a nonzero child exit code does not cancel the remainder of the operation.)
Firstly — thank you v much for
rargs
! I use it a lot. It's probably the most underrated "new cli tools" library.What should the exit code of an rargs command?
Currently it seems to return successfully even if there were lots of errors in the individual commands.
I'd like to be able to understand if any command failed (e.g. did any string fail to be grepped in a file). Is there a way of doing that with the current library?
The text was updated successfully, but these errors were encountered: