-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Add string "verbose" for -v help #1310
Comments
Maybe just add |
Sure, that would help too |
mydongistiny
pushed a commit
to mydongistiny/ninja
that referenced
this issue
Oct 1, 2019
This is a merge of upstream master up until this dep file parsing change, which will need more verification given our depfiles: ninja-build#1039 The biggest change in this merge is probably the use of 64-bit timestamps. * commit '5a78423193c48cae4800eb1ec44b62d14ae03920': (80 commits) Add OSX build on travis (ninja-build#1502) Fit --help output into 80 columns and move verbose up, fix ninja-build#1500 Improve error message when Python wasn't found for the browse tool Explain why there's no browse tool, fix ninja-build#1478 HACKING: use `Python` for the project HACKING: fix some whitespace nits Fix rendering of code block, fix ninja-build#955 Make -j 0 run unlimited parallel builds, fix ninja-build#1309 Enable ANSI escape sequences on Windows 10 terminals Add --verbose as an alternative spelling for -v, fix ninja-build#1310 Add unit test for ninja-build#1491 Allow disabling of escape code stripping, fix ninja-build#1475 subprocess-win32: add hint on ERROR_INVALID_PARAMETER Win32Fatal: support a "hint" for the error manual: mention the "invalid parameter" case util: don't add ellipses width when deciding if they're necessary Verify GetFullPathName return value Make output_test.py independent of the environment Fix older VS compatibility issues and PDB files generation issue. (ninja-build#1435) Fix parsing some special chars in depfiles ... Change-Id: I315385cecc748ff351614792a9921ec87e5f4cf3
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Usually I grep for "verbose" string to see if any command have such capabilities. I believe many do the same, because that is a commonly used term (And I missed the verbose flag because of that, which might be a funny to say).
So, it might be better to reword the help string of "-v" to include the word "verbose" somewhere.
Thanks
The text was updated successfully, but these errors were encountered: