netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dragan Simic <dsimic@manjaro.org>
To: Gedalya <gedalya@gedalya.net>
Cc: Sirius <sirius@trudheim.com>, netdev@vger.kernel.org
Subject: Re: iproute2: color output should assume dark background
Date: Thu, 23 May 2024 15:23:05 +0200	[thread overview]
Message-ID: <7d67d9e72974472cc61dba6d8bdaf79a@manjaro.org> (raw)
In-Reply-To: <449db665-0285-4283-972f-1b6d5e6e71a1@gedalya.net>

On 2024-05-23 15:04, Gedalya wrote:
> On 5/23/24 8:36 PM, Dragan Simic wrote:
>> On 2024-05-23 09:57, Sirius wrote:
>> How about this as a possible solution...
> 
> For what problem?

Obviously, for the problem your patch attempts to solve.

> Yes I asked Debian in the first place to leave colors disabled by
> default, but nevertheless `ip` is still broken for most users if and
> when colors are enabled, whether at runtime or build time.

Well, the coloring support in ip(8) can't be broken if the users
configure it at runtime accordingly, i.e. following the background
color configured in their terminal emulator(s), right?  Or am I
misunderstanding something?

>> If Debian configures the terminal emulators it ships to use dark
>> background,
> 
> Do they? Or is that the nearly universal default?

Frankly, I don't know for sure because I don't use many different
terminal emulators, but you as the submitter of this patch perhaps
should know that better.  However, terminal emulators must be
configured somehow, because it makes no sense whatsoever that they're
having their background colors hardcoded.

>> why not configure the ip(8) utility the same way, i.e. by setting
>> COLORFGBG in files placed in the /etc/profile.d directory,
> 
> COLORFGBG where set is automatically set by the terminal emulator. It
> would be more sensible to add this feature to more terminal emulators,
> upstream.

Of course, but that would take a lot of time, both to implement it
everywhere and for the new feature to reach the users.  Shipping
a few additional files in the /etc/profile.d directory would be a
reasonable stopgap measure.

> Should Debian come up with a patch that magically adjusts this
> variable every time the user changes their background color (in one
> terminal emulator... and another color in another terminal
> emulator...?)

That's a valid concern.  Perhaps some documentation could be provided,
to help the users who alter their background colors.

> And what about linux virtual terminals (a.k.a non-graphical consoles)?

In my 25+ years of Linux experience, I've never seen one with a 
background
color other than black.

> In summary, if the best we can do is manually set COLORFGBG when using
> a light background then that's the best we can do. I don't see how
> Debian can possibly help with that.
> 
> On the iproute2 side, a rock-bottom ultimate default background color
> assumption will always be needed and that should be dark.

As others already pointed out, "should be light" or "should be dark"
can be seen as personal preference.

> 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.

In an ideal world, yes.

  parent reply	other threads:[~2024-05-23 13:23 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
2024-05-28  9:40               ` Gedalya
2024-05-23 13:23           ` Dragan Simic [this message]
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=7d67d9e72974472cc61dba6d8bdaf79a@manjaro.org \
    --to=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).