3 ms·
I wish all of these initiatives luck, but for the basic Unix utilities they couldn't even agree on some sort of common format to allow for introspection (i.e. t
by oblio 6y ago
I wish all of these initiatives luck, but for the basic Unix utilities they couldn't even agree on some sort of common format to allow for introspection (i.e. the tool itself would allow for the extraction of its parameter names, parameter types, etc.).
I somehow feel that all these boil-the-oceans approaches regarding rich CLIs aren't going to make it very far.
Which is really unfortunate :-(
- laumars 6y agoYou don’t need to cover every parameter and use case of every command. You just need to cover the most common use cases and give them priority over the more esoteric flags. So beginners get help but power users can still use the shell. I say “just” but obvious even that is still a big task. As for covering every flag for every tool, some shells already parse man pages and —-help output to provide meaningful autocompletions automatically. Murex does this (https://murex.rocks https://murex.rocks) as does fish (https://fishshell.com https://fishshell.com)
- donio 6y agozsh supports extracting options from the command's --help output and it even recognizes when FILE or DIR is specified as the argument for an option. There is probably something like that for bash too.