On Wed, Feb 01, 2017 at 11:55:53AM +0100, Markus Trippelsdorf wrote:
> On 2017.02.01 at 11:48 +0100, Jakub Jelinek wrote:
> > On Wed, Feb 01, 2017 at 11:45:14AM +0100, Markus Trippelsdorf wrote:
> > > Some colors on e.g. https://gcc.gnu.org/gcc-7/changes.html are nearly
> > > unreadable. So what about the following patch?
> > >
> > > --- gcc_orig.css 2017-02-01 11:39:17.634017498 +0100
> > > +++ gcc.css 2017-02-01 11:40:23.979244263 +0100
> > > @@ -58,8 +58,8 @@
> > > }
> > > div.copyright p:nth-child(3) { margin-bottom: 0; }
> > >
> > > -.boldcyan { font-weight:bold; color:cyan; }
> > > -.boldlime { font-weight:bold; color:lime; }
> > > +.boldcyan { font-weight:bold; color:#25a9a9; }
> > > +.boldlime { font-weight:bold; color:green;}
> > > .boldmagenta { font-weight:bold; color:magenta; }
> > > .boldred { font-weight:bold; color:red; }
> > > .boldblue { font-weight:bold; color:blue; }
> >
> > I think the intent is that they actually match closely what gcc/libasan
> > emits
> > (that of course depends on the exact terminal setting).
> > So are your colors closer to what gcc/libasan print or not?
>
> As you said, the exact terminal colors are user definable.
> But yes, the change above bring them closer to what I see in my
> terminal.
Exactly the opposite here, the current colors match very closely what I get
(gnome-terminal, White on black, Linux console color set),
your colors are completely different.
E.g. in changes.html, the Asan spans with boldlime are using
\033[1m\033[32m
in libsanitizer, and the note color in gcc by default is
\033[1m\033[36m
I've tried various color settings of gnome-terminal (both white on black and
black on white plus the different color sets) and all of them except
for Solarized (which is shades of grey) look much brighter than your colors.
Jakub
