Comment 7 for bug 996401

> What purpose does `bzr config <option>` server other than to show the user what the option is set to?

No other but that's an important use case not covered otherwise.

'bzr config --all option' serves a different purpose: it tells the user where the option is defined (in any config file) and how default/override definitions interact.

Also, 'bzr config option' is the shortest syntax *because* it's meant to be used in scripts:

   bzr push `bzr config mypush`

Forcing the user to use --expand won't be friendly.

Finally, 'bzr config' itself defaults to 'bzr config --all .*' and that's what people are expected to use to start with.