It instructs the user to use '-vh' when the user has already done that.
So what? Consider that this help is going to be a manual. If you do not
display -vh in long-help then it will not appear in manual. And if you do,
then it is going to be fine. And logical. And fit perfectly. Once again, if
user takes effort to write -vh, or --verbose --help for that matter, it means
they mean that, they know what they are doing, and expect to get full, long
help and do not need to be educated on that topic. From my experience, every
time I looked at long help option, whether in compressor of ffmpeg or any other
program, I never checked how to call help - that was the last thing I was
looking for. For simple reason - I already knew how to call it and was looking
for some other information that is not in short help and did not care about
calling long-help whatsoever. But I think I have found the simplest and most
elegant solution (no need for --verbose, extra options, or fixed order of
options): -h display usage help and exit
--help display full help and exit I do not like it. It is
not exactly correspond with the GNU coding standards* that state: > The
standard --help option should output brief documentation for how to invoke the
program I emphasize _brief_ documentation. Elaborate one should be
reserved for more elaborate option (here -v --help). GNU Coding Standards
www.gnu.org https://www.gnu.org/prep/standards/standards.html#g_t_002d_002dhelp
