Here is one of your empty argument being thrown away instead of respected bugs:
* https://github.com/spf13/cobra/blob/6dec1ae26659a130bdb4c985...
I could explain the single-quote argument quoting error if you were running it on Windows. The Go runtime library does not provide single-quoting on Windows. At all. (This is historically the behaviour of C runtime libraries on Windows, too.) It should be using a proper argument vector and not doing its own command-line parsing on other platforms, though.
* https://cs.opensource.google/go/go/+/master:src/os/exec_wind...
* https://cs.opensource.google/go/go/+/master:src/os/proc.go;l...
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.