One way to prevent option processing after a command-line argument that is not an option is to use a double hyphen "--" before the non-option argument. This tells the command-line interpreter that any subsequent arguments should be treated as non-options, even if they begin with a hyphen.
For example, in the command:
$ command --option1 --option2 file.txt
the double hyphen tells the interpreter to treat "file.txt" as a non-option, even though it does not begin with a hyphen. The command will process the options "--option1" and "--option2" but will not attempt to interpret "file.txt" as an option.
Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss
Asked: 2023-06-24 16:11:49 +0000
Seen: 8 times
Last updated: Jun 24 '23
What is the meaning of "version list argument cannot be empty"?
How can the argument of Jest Mock Service be made assignable?
What is the method for configuring a single default argument in pybind11?
How can the error "Missing 1 required positional argument: 'number'" be restated?
The ASP.NET Core MVC HTTP post method is receiving a null argument from an Angular call.
The keyword argument 'normalize' was not expected in the __init__() method of Ridge.
Why is the solution for Ansible SSH user/pass Invalid Argument leading to host unreachability?