3 ms·
I think the most important piece here is standardizing a schema format for command line programs. Once you have that (and it’s actually adopted) there are many
by brap 3y ago
I think the most important piece here is standardizing a schema format for command line programs.
Once you have that (and it’s actually adopted) there are many possibilities. TUI/GUI is just one of them. Think autocomplete, type checking, discoverability...
- tuchsen 3y agoAh I'm reminded of that one xkcd. https://xkcd.com/927/ https://xkcd.com/927/ I hate to be the LLM guy but they're really good at processing semi-structured data to structured data. You could go that route and have a universal autocomplete for the CLI. Kinda like Co-Pilot for Bash, or you could use it to do what the parent's doing and have a universal TUI program for building commands.
- willm 3y agoI think so to! The schema has possibilities beyond just this tool.
- d0mine 3y agoCommand-line interface description language http://docopt.org/ http://docopt.org/
- hprotagonist 3y agowith, infamously, no spec.
- bee_rider 3y agoIs this what the Click library that Torgon uses provides?
- fbdab103 3y agoI believe something of this nature was proposed in the Oilshell under the name Shellac[0]. A shell-agnostic autocompletion format so that the world could finally move on from writing bespoke completion protocols for every new shell language. [0] https://github.com/oilshell/oil/wiki/Shellac-Protocol-Proposal https://github.com/oilshell/oil/wiki/Shellac-Protocol-Propos...
- alex_hirner 3y ago> schema I'm dreaming of a universal standard based on JSON Schema. Dynamicity is a challenge of course. I guess one needs to strike a balance between static data, say for each subcommand, and a full blown configuration language, say nix.