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
Also try the version
sub-command
#12
Comments
Possibly related: ffmpeg (and the whole ff- family) uses |
For anyone that wants to work on this, see the initial attempt and feedback in #13. |
@issuehunt has funded $40.00 to this issue.
|
@sindresorhus has rewarded $36.00 to @stroncium. See it on IssueHunt
|
For the record, I did try it on every possible command in my system, and after waiting for an hour and closing hundreds of windows I can say I'm fairly satisfied with result: nearly half of commands did produce a version, and a lot of ones which didn't are gui-only tools which aren't supposed to have one(though I didn't check manually) and some obscure names(so internal utils, I suppose). NOTE: don't recommend to reproduce it, my system is nearly destroyed atm, and that's just what I see from a glance. |
Thanks doing such thorough testing 👌 |
Some binaries, like
$ openssl
, show the version using a sub-command$ openssl version
instead of a flag like$ curl --version
. If no arguments are given, it would be useful to first tryfoo --version
and thenfoo version
.We should also hard-code a list of common binaries that use the
version
sub-command, so we try that first for those. For improved performance. Binaries like,openssl
,swiftlint
, etc.IssueHunt Summary
stroncium has been rewarded.
Sponsors (Total: $40.00)
Tips
The text was updated successfully, but these errors were encountered: