But, aside from that, I'm coveting this right now as I hack away with adding new options to my C++ program...
Anyway, once I think of a better example I'll swap it in. Thanks for your input!
This is quite an elegant piece of software, and your readme is doing it little service.
I wonder how hard it would be to make my 'shkeleton' CLI parser embeddable -- it's basically argparse for bash scripting right now. [2]
Well, my definition of "embeddable" is a very loose one. All you really need to be able to do is allow the user to specify in/out/err streams, so that they could be anything: a log file, a socket, a Python function, etc. So maybe keep a var for each of these and redirect the echos to them?
> For example, Click has integrations for fetching terminal dimensions and setting environment variables. This may be useful, but it also means trying to use Click for an embedded CLI (say, one running in a text editor communicating via websockets) is extremely difficult.
https://github.com/willyg302/clip.py/blob/master/docs/index....
1. https://github.com/willyg302/clip.py/blob/master/docs/main.m...
Just thinking about it.
Could you elaborate on this? Do you mean user input more like natural language? I've seen a few attempts at this such as betty [1], but the reality of it is the input must still be translated into something the CLI understands, and as you might imagine it becomes difficult for more obscure options.
I didn't meant something so abrangent, I meant something simpler. For example, `ls`:
Instead of `ls -l`, `ls complete` or `ls with metadata`.
Instead of `ls -L`, `ls following symlinks`.
Instead of `ls -a`, `ls all` or `ls with all`.
I don't remember exactly what I was thinking.
