But when bouncing along and exploring, one comes across a uwtwrapper call within an anondist script, so one naturally does … uwtwrapper --help to find out what the command is / does. Hopefully it gives a concise description then parameter list.
One then runs the anondist verbose to see how the script is being called … to go - OH, so that’s how they’re doing that. Cool.
And gets on with their day.
But can’t if --help doesn’t do the USUAL.
If you want to contribute a wrapper
My point is, I wouldn’t have to exit my workflow and read any of it if --help responded with the usual then and there. As you point out, it’s all scripting, and easily followed (if --help and man conventions are followed). One of the real pluses attributed to Linux is configuration files being text and so much scripting one can figure out most things on the fly then and there.
Similarly … hmmm, this would be useful, ssh does it this way, let’s command line run see if we can make this work. (And you’re going to want --help to return concise useful stuff then and there.) Hey it works, let’s encapsulate it in a script. Hmm, it really is useful, maybe I should go check in on to how to contribute it back up the chain.
All I have pointed out is that you can save a lot of time and energy, let alone the time spent on this thread, with a typical --help. If I did it, so will others.
Even if all --help returns is: ‘uwtwrapper encapsulates uwt calls. See uwt for more info.’, the job is done.
Now … would you like to go around again for ‘uwt --help’?
uwt -h does exactly what I was expecting of uwtwrapper --help.
Except … there it is -h doing what by convention --help does. (Hint.)