RFC: Coloured output in bazaar core

[Martin Pool]

On Mon, Aug 4, 2008 at 10:39 PM, John Arbash Meinel
<john at arbash-meinel.com> wrote:
> I would just argue that it changes the command line options as well.
> Specifically, the standard options are usually:
>
> foo --color=never/always/auto
>
> Which is different from
>
> foo --color
> foo --no-color

I agree.  It might be nice to support --no-color === --color-never but
that's kind of a frill and should also wait til later.

> |
> | For what it's worth, git's colour configuration and options appear to
> | use the US spelling exclusively.
>
> As does "ls --color" it seems grep allows both --color and --colour.
>
> The biggest problem is that if you make it a *branch* config, then you
> can override it in a per-branch config. Which runs into problems of
> having "color=always" in branch.conf, and "colour=never" in branch.conf.
> ConfigObj is also helpful about indicating when you have the same option
> written twice, but can't be of help when they are spelled differently.

Exactly.  I'm not saying I would object to adding the alias later if
it's done in a tasteful way, getting all of this correct, but I think
it's nontrivial enough it would be better to get the actual feature
working and merged first.

> As for the Bazaar internals, they should all be "get_color", I believe I
> remember Martin indicating that US spelling is preferred for all internals.

Right, even though I'm both a British and Australian citizen and so
ought to have twice as strong a preference for having the 'u'. :-)  I
think it is much more standard in technical use.

-- 
Martin <http://launchpad.net/~mbp/>