netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sirius <sirius@trudheim.com>
To: Dragan Simic <dsimic@manjaro.org>
Cc: Gedalya <gedalya@gedalya.net>, netdev@vger.kernel.org
Subject: Re: iproute2: color output should assume dark background
Date: Thu, 23 May 2024 15:02:06 +0200	[thread overview]
Message-ID: <Zk8-Tq733F8pgMB4@photonic.trudheim.com> (raw)
In-Reply-To: <e4695ecb95bbf76d8352378c1178624c@manjaro.org>

In days of yore (Thu, 23 May 2024), Dragan Simic thus quoth: 
> On 2024-05-23 09:57, Sirius wrote:
> > Maybe colouring the output by default isn't such a wise idea as
> > utilities reading the output now must strip control-codes before the
> > output can be parsed. Why not leave it as an option via the -c[olor]
> > switch like before?
> 
> How about this as a possible solution...  If Debian configures the
> terminal emulators it ships to use dark background, why not configure
> the ip(8) utility the same way, i.e. by setting COLORFGBG in files
> placed in the /etc/profile.d directory, which would also be shipped by
> Debian?

That makes more sense.

> That wouldn't be a perfect solution, of course, but would be more
> consistent.  Debian ships terminal emulators configured one way, so the
> ip(8) should also be shipped configured (mind you, not patched) the same
> way.

This is a much better argument - Thank you. Something for the
distributions to consider should they turn on the colour by default.

-- 
Kind regards,

/S

  reply	other threads:[~2024-05-23 13:02 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 [this message]
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
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=Zk8-Tq733F8pgMB4@photonic.trudheim.com \
    --to=sirius@trudheim.com \
    --cc=dsimic@manjaro.org \
    --cc=gedalya@gedalya.net \
    --cc=netdev@vger.kernel.org \
    /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).