Add support for long options with double hyphen in dita command
See original GitHub issueTo follow the UNIX convention in command arguments, long option form should start with double hyphen. For backwards compatibility, the single hyphen form should be retained. After the change, the following commands are equivalent:
$ dita -install
$ dita --install
Issue Analytics
- State:
- Created 7 years ago
- Comments:14 (14 by maintainers)
Top Results From Across the Web
Arguments and options for the dita command
Note: Most dita command options support several syntax alternatives. All options can be specified with a GNU-style option keyword preceded by two hyphens....
Read more >Support for single hyphen in long arguments #1210 - GitHub
Hi, I would like to begin porting a piece of command line software to rust which uses arguments of the style "-argument" with...
Read more >for single-character options, but double dashes `--` for words?
If I read a double dash, --, then the rest of the command line argument must match a single option. I just recently...
Read more >What Does a Double-Dash in Shell Commands Mean?
A double-dash in a shell command signals the end of options and disables further option processing. Let's see this in action using the...
Read more >Git commands with double dashes - Stack Overflow
Double dashes are standard for long options. – ziu. May 6, 2014 at 14:04. possible duplicate of ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Should we also extend the CLI syntax so that you could set parameters directly with the long form? That is, the following would be equivalent
The long form option would only be available for parameters configured in plugin configuration file; the
-D
form would allow non-configured parameters.The backwards compatibility layer would need to be at Ant level, not CLI (
dita
command), because not all users use CLI.