docopt.sh VS prompt.gem

I like that this generates readable output that could pass as hand-written code.

The docopt.sh output looks like it went through a JS minifier. Or is there a way to change that? If so I think it should default to that.

https://github.com/andsens/docopt.sh/blob/master/docs/naval_...

If you want to avoid having to write your own args parser everytime or think getopt is a pain, you should check out my little project:

https://github.com/andsens/docopt.sh

No dependencies, the code is directly inlined into your script, and you write the args parser by writing the help-text.

Honestly, I left it as a gist because even though it reduces boilerplate, getopts is still not a great flag parser (e.g. only supports single-letter flags, and no type safety or other validation aside from boolean / string). I use it in my shell environment since I have lots of shell functions and I don't care to pull in a "real" parser into my shell, but if I was writing any sort of more complex standalone script I probably wouldn't use it. Check out docopt if you haven't seen it, I've been meaning to give that a whirl at some point.

And like many I've spent waaay too long messing around with my shell environment, which has wound up as ProfileGem, a modular shell environment manager, along with prompt.gem, my custom terminal prompt. Some features that stand out:

I've been using this library for years to make my terminal prompt more zippy. It takes advantage of a number of unusual techniques that folks might find interesting.