Skip to content

Document built in command switch behavior #5302

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

Merged
merged 1 commit into from
Apr 28, 2025
Merged

Conversation

Supreeeme
Copy link
Contributor

No description provided.

a single dash (*-*) will be interpreted to be a switch up until the first
parameter that doesn't start with a single dash. Any unknown switches will
cause an error. To force the remaining parameters to not be interpreted as
switches, you can pass two dashes (*--*) as a parameter.
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure this properly describes how switches work, it is command dependent if switches have to be first argument or not for example, and show switches take parameters while other do not. I think this should be reworded to reflect that.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for the delay. I reworded it a bit.

@mawww mawww merged commit d48713a into mawww:master Apr 28, 2025
4 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants