We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As stated in the cli-guidelines, cli arguments should order-independent.
Not just the cli-guidelines, it is also very common for cli program to not have order-dependent arguments, as that can confuse user
This confuses me the first time when I can't just do
rip search qobuz track "die with a smile" -ndb
And, it turns out, the -ndb argument is only valid on the first argument,
-ndb
rip -ndb search qobuz track "die with a smile"
This will confuse many users because rip search currently supports
rip search
rip [OPTION] search [OPTION]
But when we do rip search --help it doesn't mentioned the first [OPTION]
rip search --help
[OPTION]
$ rip search --help Usage: rip search [OPTIONS] SOURCE MEDIA_TYPE QUERY
I would like streamrip to have their cli arguments as order-independent
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is the feature request related to a problem. Please describe it.
As stated in the cli-guidelines, cli arguments should order-independent.
Not just the cli-guidelines, it is also very common for cli program to not have order-dependent arguments, as that can confuse user
This confuses me the first time when I can't just do
And, it turns out, the
-ndb
argument is only valid on the first argument,This will confuse many users because
rip search
currently supportsBut when we do
rip search --help
it doesn't mentioned the first[OPTION]
Describe the solution you would like.
I would like streamrip to have their cli arguments as order-independent
Describe alternatives you've considered.
No response
The text was updated successfully, but these errors were encountered: