Brandon Casey [off-list ref] writes:
Currently, when parse_options() produces a help message it always emits
a blank line after the usage text to separate it from the options text.
If the option spec does not define any switches, or only defines hidden
switches that will not be displayed, then the help text will end up with
two trailing blank lines instead of one. Let's defer emitting the blank
line between the usage text and the options text until it is clear that
the options section will not be empty.
This somehow looks familiar. I think (together with the fix in 2/3)
this makes it definitely better.
I also wonder if we want the final blank line, but that is sort-of a
different issue.
Thanks.