ping @SvenDowideit @shykes

much ❤️ Docs LGTM

@tianon typo updated

ping @shykes @crosbymichael @creack

Hmm, why? It is pretty painful to write --flag=false whereas --no-flag is straight forward and pretty.

@creack see #5545, @SvenDowideit is confused by --no-flag=false

This is a conflict between documentation and usability. Having to manually specify the value to the flag really makes usability worse. --no-flag is binary, either it is present either it is not. You don't need to worry about its value, so there is no double negative.
ping @SvenDowideit

With #5764 that I did on top of this one, using --no-trunc is effectively shorthand for --trunc=false, but --no-trunc=false literally won't parse (ie, if the flag we're parsing has a value attached via =, we don't even check whether it's got the -no prefix).

@vieux and @creack yes - the confusion I'm talking about is in how the help for the option is laid out, not so much the actual usage.

Specifically, read -D, --debug, --no-debug (=false) Enable debug mode and notice that it does infact tell the reader that --no-debug (=false) is something. While someone that knows Docker will realise that you're saying that the default is --debug=false or --no-debug that's not what is written.

Its even more amusing, given that if someone reads the entire line as a single sentence, it becomes very true again - IFF you ignore the braces:

Using -D, --debug or --no-debug=false will enable debug mode.

I agree - that fugly syntax was my first-pass attempt to show whether we're enabled or disabled by default. I think swapping that to (default: enabled) or (default: disabled) would help (which would be reasonably simple to do).

The motivation seems to be to solve #5545. However that issue is really about clarity of the usage message,
not syntax of the flag itself.

Since breaking a flag is always extra work and complication, we should only do it if there's a strong
enough reason. I don't think there's a very strong reason in this case. It seems to me we could
just fix the usage message to not print '=false' and we should be good.