|
|
|
|
|
by arp242
361 days ago
|
|
Alignment (and maybe bold text for some things) is all you need in >95% of cases, IMHO. One of the downsides of a lot of these tools is that's exactly what they don't do well: many things don't align or wrap nicely. For example, here's a comparison of this fang library vs one where I just raw-dogged the usage text: https://imgur.com/a/QWh9TLD – the nice alignment does a lot more than colours. Especially for larger programs with a bunch of flags it can be such a pain. For example from an otherwise quite nice tool: https://imgur.com/a/RELL9Gk – you just completely lose any "overview". I did spend some time on some better tooling to improve all of this, because manually writing these isn't super-fun either, but not so straight-forward to do well (or at least: not in a way that I like). |
|
Bling is easy. Unsexy usability details are hard.
Why would an example program take 228ms? Huh? 'abc def' is one shell word. --name=abc works fine. But I did give it an argument: the empty string.And why is the output indented two columns from the left margin anyway?
Should have produced an error using '' for the subcommand name. Huh? Why did the command work when I typed it myself but not when I pasted from the help output?Oh. Because the help output is using nbsp, not regular spaces.
Anyway, command line interfaces have a surprising number of hairy corner cases. I'd rather have boring monochrome that gets them right than an all-colorful theme auto-shell-completion-generating system that doesn't.