comparison tests/test-pager.t @ 32026:57042e91521a

color: turn on by default (but for windows) Color support is all in core for a couple of months. I've browsed the bug tracker without finding any blocker bug. So I'm moving forward and enable color on by default before '4.2-rc'. In the worse case, having it on in the release candidate will help us to find blocker bug and we can turn it off for the final release. I remember people talking about issue with Windows during the freeze so I'm keeping it off by default on that OS. We could do various cleaning of the color used and the label issued. However the label are probably already in our backward compatibility envelope since the color extensions has been around since for ever and I do not think the color choice themself should be considered BC. So I think we should rather gives color to all user sooner than later. A couple of test needs to be updated to avoid having color related control code spoil the tested output.
author Pierre-Yves David <pierre-yves.david@ens-lyon.org>
date Sun, 16 Apr 2017 02:32:51 +0200
parents d323d9e0d7b4
children 05cdd5678c6b
comparison
equal deleted inserted replaced
32025:d323d9e0d7b4 32026:57042e91521a
8 pager and tell it to use our fake pager that lets us see when the 8 pager and tell it to use our fake pager that lets us see when the
9 pager was running. 9 pager was running.
10 $ cat >> $HGRCPATH <<EOF 10 $ cat >> $HGRCPATH <<EOF
11 > [ui] 11 > [ui]
12 > formatted = yes 12 > formatted = yes
13 > color = no
13 > [pager] 14 > [pager]
14 > pager = python $TESTTMP/fakepager.py 15 > pager = python $TESTTMP/fakepager.py
15 > EOF 16 > EOF
16 17
17 $ hg init repo 18 $ hg init repo