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
{{ message }}
This repository has been archived by the owner on Sep 14, 2023. It is now read-only.
The above program works fine (cargo run -- subcommand arg). However, if the subcommand is changed to start with the binary name (new usage string: prog progsubcommand <arg> ), running cargo run -- progsubcommand arg will fail with 'Invalid arguments...'. But running cargo run -- subcommand arg will again work. The problem does not occurr on http://try.docopt.org/.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm not sure whether this is expected behavior, but the following seems a bit strange to me:
The above program works fine (
cargo run -- subcommand arg
). However, if the subcommand is changed to start with the binary name (new usage string:prog progsubcommand <arg>
), runningcargo run -- progsubcommand arg
will fail with 'Invalid arguments...'. But runningcargo run -- subcommand arg
will again work. The problem does not occurr on http://try.docopt.org/.The text was updated successfully, but these errors were encountered: