All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Gedalya <gedalya@gedalya.net>
Cc: Dragan Simic <dsimic@manjaro.org>, Sirius <sirius@trudheim.com>,
	netdev@vger.kernel.org
Subject: Re: iproute2: color output should assume dark background
Date: Thu, 23 May 2024 07:59:04 -0700	[thread overview]
Message-ID: <20240523075904.16f3599b@hermes.local> (raw)
In-Reply-To: <94d43b6d-74ae-4544-b443-32d8da044b75@gedalya.net>

On Thu, 23 May 2024 22:33:03 +0800
Gedalya <gedalya@gedalya.net> wrote:

> On 5/23/24 10:24 PM, Dragan Simic wrote:
> > I had in mind setting COLORFGBG to dark background that way, not some
> > shell magic that would change it dynamically.   
> 
> It's far far easier to just do color palette overrides in your terminal 
> emulator.
> 
> The "Dark Pastels" preset in XFCE Terminal makes everything just work. 
> Both iproute2 palettes work fine.
> 
> Anyone who really cares about colors can and should dive into the topic 
> (not me). Once your graphical desktop is up and configured you'll be 
> just fine.
> 
> The only real issue here is force-enabling colors where they are least 
> welcome (crashed server, vt, no mouse, black background, just let me do 
> my work please).
> 
> This entire discussion has gone way way way out of control.

Fits perfect with "what color for the bike shed"

  reply	other threads:[~2024-05-23 14:59 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
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 [this message]
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=20240523075904.16f3599b@hermes.local \
    --to=stephen@networkplumber.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.