> What I had in mind was more of a shell script In my opinion, that's awkward.
Maybe it might prove to be that, but I find the current situation very awkward and prone to bugs. > or whatever that accepts the platform specific > syntax, and has something machine readable to processes before > printing it to the user. Do you envision this "whatever" to be an external wrapper program which constructs the new command line and invokes the proper utility, or some kind of a library call that does the command line translation prior to invoking argp_parse? External wrapper was my thought. This would only be fore `weirdo' command line syntaxes, so you would always need to parse the arguments manually in either case.
