Hi Mark and Klemens, Mark Kettenis wrote on Thu, Jan 16, 2020 at 02:46:02PM +0100:
> I suppose this is fine since vmctl(8) has the same option. > > However the way you change the usage output isn't quite right. > Maybe "start" should go on a line of its own then. That sounds reasonable. > But then we're back to the discussion that too many lines make the > usage output useless. I'm among the people who dislike excessive usage() messages, but going from six to seven lines when that is necessary to preserve correctness and completeness doesn't feel excessive to me. > Maybe just leave the usage strings alone? I don't object to either solution. Besides, i think doubt regarding the docomentation should not prevent a simple feature from going in, in particular not if it is documented in the same way as existing features. In this case, that would mean putting "start" onto its own line, because right now, commands are combined into one line if and only if they share the same options and arguments. Even if the features of a program grow so much over time that at some point, existing practice in the documentation becomes awkward, then the documentation can be reorganized separately, without impeding the development of useful new functionality. Yours, Ingo
