Michael van Rooijen

Thanks for the great input! Working on these changes now.

One problem regarding having `` in `-p, --port `. All flags have defaults, so no `required` option has been implemented. The reasoning behind it at the time was that I...

Perhaps unnecessary to render `-p, --port [port]` since the `default: 8080` is already present, which implies that it's optional.

There's no way to infer that you want a directory (`DIR`) as an argument to `--cache` (it'd infer `` which doesn't help, and wouldn't work if there was only a...

Note that `DIR` in short/long doesn't do anything. It's purely there to add additional information on what argument to provide to the flag and render that in the help screen.

Alternatively, and much easier to implement and perhaps more understandable would be to allow you to specify a flag arg: ```crystal cmd.flags.add do |flag| flag.name = "cache" flag.short = "-c"...

I opted for what you intuitively tried. It's more consistent with how you define a command, so to avoid inconsistencies we'll use the same notation style with flags. I ended...

Nice. I wasn't aware of `tput` nor `stty`. I was aware of `ENV["COLUMNS"]` and `ENV["LINES"]` but these are apparently not always available. In any case we could at least provide...

Looking at `docker help`, they keep it all on a single line for both commands and flags, and the flags wrap, while the commands don't. I think I'm currently leaning...

I've opened 3 new issues where these additions can be discussed. If you have any specific DSL/Output ideas for Commander for these specific features, submit them there.