From: David Laight <David.Laight@ACULAB.COM>
To: 'Sirius' <sirius@trudheim.com>, Gedalya <gedalya@gedalya.net>
Cc: Dragan Simic <dsimic@manjaro.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE: iproute2: color output should assume dark background
Date: Tue, 28 May 2024 09:07:42 +0000 [thread overview]
Message-ID: <9e1badfc5d3d47afbdd362c9e6faa01b@AcuMS.aculab.com> (raw)
In-Reply-To: <Zk9CehhJvVINJmAz@photonic.trudheim.com>
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)
next prev parent reply other threads:[~2024-05-28 9:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 19:21 iproute2: color output should assume dark background Gedalya
2024-05-22 19:27 ` Dragan Simic
2024-05-23 6:39 ` Sirius
2024-05-23 7:08 ` Gedalya
2024-05-23 7:57 ` Sirius
2024-05-23 8:05 ` Sirius
2024-05-23 12:36 ` Dragan Simic
2024-05-23 13:02 ` Sirius
2024-05-23 13:04 ` Gedalya
2024-05-23 13:19 ` Sirius
2024-05-23 13:47 ` Dragan Simic
2024-05-28 9:07 ` David Laight [this message]
2024-05-28 9:40 ` Gedalya
2024-05-23 13:23 ` Dragan Simic
2024-05-23 13:39 ` Gedalya
2024-05-23 14:02 ` Dragan Simic
2024-05-23 14:11 ` Gedalya
2024-05-23 14:24 ` Dragan Simic
2024-05-23 14:33 ` Gedalya
2024-05-23 14:59 ` Stephen Hemminger
2024-05-23 15:17 ` Gedalya
2024-05-23 13:50 ` Gedalya
2024-05-23 14:07 ` Dragan Simic
2024-05-23 14:13 ` Gedalya
2024-05-23 14:26 ` Dragan Simic
2024-05-23 14:11 ` Sirius
2024-05-23 14:19 ` Gedalya
2024-05-23 14:28 ` Dragan Simic
2024-05-23 14:29 ` Dragan Simic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9e1badfc5d3d47afbdd362c9e6faa01b@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=dsimic@manjaro.org \
--cc=gedalya@gedalya.net \
--cc=netdev@vger.kernel.org \
--cc=sirius@trudheim.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).