It has long been a pet peeve of mine that the *nix world has no standard reliable convention for how to interrogate a program for it's available flags. Instead there are at least a dozen ways it can be done and you can't rely on any one of them.
It has long been a pet peeve of mine that the *nix world has no standard reliable convention for how to interrogate a program for it's available flags. Instead there are at least a dozen ways it can be done and you can't rely on any one of them.
I've been thinking about using an OpenAPI schema to describe cli tools. It would probably need extensions to describe stdin/stout and other things that don't happen in REST.
Have you seen Stainless's CLI generator?
https://www.stainless.com/blog/stainless-cli-generator-your-...
That's not specific to unix though.
I didn't say it was, but I simply don't care what problems any other kind of system has because they aren't my problems. Last time I had windows on any of my computers it was windows 98.
With the right DOS flags, Windows 98 had pretty well standardised on /?. Of course, when you changed those flags, some programs would stick with their hardcoded /?, others would change to -?, and yet others would just fall over.