[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9e1badfc5d3d47afbdd362c9e6faa01b@AcuMS.aculab.com>
Date: Tue, 28 May 2024 09:07:42 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Sirius' <sirius@...dheim.com>, Gedalya <gedalya@...alya.net>
CC: Dragan Simic <dsimic@...jaro.org>, "netdev@...r.kernel.org"
<netdev@...r.kernel.org>
Subject: RE: iproute2: color output should assume dark background
From: Sirius
> Sent: 23 May 2024 14:20
>
> In days of yore (Thu, 23 May 2024), Gedalya thus quoth:
> > Yes, echo -ne '\e]11;?\a' works on _some_ (libvte-based) terminals but not
> > all. And a core networking utility should be allowed to focus on, ehhm,
> > networking rather than oddities of a myriad terminals.
>
> Then it perhaps should not add colour to the output in the first place and
> focus solely on the networking.
>
> A suggestion would be the iproute2 package revert the option to compile
> colourised output as default, sticking to plain text output as that
> require zero assumptions about the user terminal. Carry on offering the
> '-c' switch to enable it at runtime.
+42 :-)
An alias in .profile can add -c - leaving it easy to turn off.
Especially for those of us who get fed up of garish colours.
gdb is pretty impossible to use these days - blue on black ???
Syntax colouring in vi make the code look like paint has been
spilt on the page - wouldn't be too bad if it was subtle (and correct).
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
Powered by blists - more mailing lists