On Mon, 2018-08-20 at 10:03 +0200, Boris Feld wrote:
> # HG changeset patch
> # User Boris Feld <boris.f...@octobus.net>
> # Date 1534290303 -7200
> #      Wed Aug 15 01:45:03 2018 +0200
> # Node ID 4144148d7aba13ece916c6f735c791ca3d93a249
> # Parent  c62184c6299c09d2e8e7be340f9aee138229cb86
> # EXP-Topic color-warning
> # Available At https://bitbucket.org/octobus/mercurial-devel/
> #              hg pull https://bitbucket.org/octobus/mercurial-devel/
>  -r 4144148d7aba
> color: issue warning in yellow
> 
> Using a different color for warning/error output help them to stand
> out and
> attract user attention. At Octobus we have been using this setting
> for years
> with good result.
> 
> Now that `ui.error` are colored in red, it seems reasonable to color
> all other
> error output in yellow.

I'm not very fan of this. Too much colors makes too much user
distraction. Each time I must use npm I scratch my head against all
these colors / styles used in the terminal. See [0]

Let's keep it simple, user can change this by itself, don't make
Mercurial too glassy/shiny/whatever adj you want :-)

[0]: 
https://cdn-images-1.medium.com/max/1600/1*0Io2KrHWz7XFw8GABaB9-w.png

-- 
David

_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel

Reply via email to