[PATCH 5 of 6 V2] ui: add color extension to progressive mode

[Matt Mackall]

On Fri, 2015-04-10 at 19:26 +0200, Mathias De Maré wrote:
> On Wed, Apr 8, 2015 at 9:40 PM, Matt Mackall <mpm at selenic.com> wrote:
> 
> > On Tue, 2015-04-07 at 21:00 +0200, mathias.demare at gmail.com wrote:
> > > # HG changeset patch
> > > # User Mathias De Maré <mathias.demare at gmail.com>
> > > # Date 1427229798 -3600
> > > #      Tue Mar 24 21:43:18 2015 +0100
> > > # Node ID 431cc24028deada0e3bbc55ff3dee7d962caa922
> > > # Parent  44f6145dde0d844a019c968a6bc5eeddadec533e
> > > ui: add color extension to progressive mode
> >
> > If we want to go this way, we probably want to pull the color extension
> > fully into core first so that it's only a command-line switch away.
> >
> What is the usual approach for this? Doing a combined check for either the
> switch or the extensions.color selection?

Move the bulk of the code into core, including the global options,
leaving behind a stub extension that sets the default to on.

> > BTW, the number one thing _I_ want to see in progressive (and one of the
> > few reasons I'm entertaining the idea) is removal of the 'tip'
> > pseudo-tag.
> >
> That's still in progress, not quite there yet. I'd like to fix that as well
> though.
> 
> In general, I'll need to see if I can do another submission of this patch
> series in the next few days, it may have to wait for the next release...

Almost certainly, as I expect to be overwhelmed shortly.

-- 
Mathematics is the supreme nostalgia of our time.