Hi Mark - thanks for the report.
it seems to me that the least bad approach is to correct the
documentation and usage messages to describe it accurately, with a
historical note in the manual explaining the long-standing error in
previous versions of the documentation.
I agree. Wou
This is sort of a follow-up on #22445; alas, nobody involved with that
bug noticed the actual scale of the problem. I'm sorry to be the bearer
of bad news.
In essence, #22445 observed that the usage message printed by
`test-driver' showed option arguments attached to their options with an
`=' sig
