-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Stricter command line parsing #56294
Comments
Could probably be folded into #29669 |
I think this is slightly different, and the minimal thing — erroring if a |
Requiring an Try (e.g. in zsh):
(However, some shells, e.g. bash-5.0 on Ubuntu, have been configured to autocomplete after |
I'm not suggesting requiring |
We could error if the long opt value starts with -, but that would probably also still be breaking |
Note that the POSIX standard says in Section 12.2 Utility Syntax Guidelines:
The convention of optionally also allowing the |
It would be nice if
=
was required instead of optional for flags with arguments. This would make the following behavior error:Motivated by #56285
The text was updated successfully, but these errors were encountered: