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 16:26:06 +0200 [thread overview]
Message-ID: <db3e76a601cec0a42cf814d870206bd4@manjaro.org> (raw)
In-Reply-To: <1b404d0c-d807-4410-b028-f606d7182789@gedalya.net>
On 2024-05-23 16:13, Gedalya wrote:
> On 5/23/24 10:07 PM, Dragan Simic wrote:
>> I think it would be best to start a gargantuan quest for having
>> COLORFGBG
>> set properly for all kinds of different terminal emulators. Including
>> the
>> Linux virtual console, which may come last.
>
> And you'll still need a default and the default will at all times be
> _something_, and it being that something would be justified by..
> well.. something?
As you proposed a bit earlier, no COLORFGBG set would mean no coloring,
regardless of what the user requested.
next prev parent reply other threads:[~2024-05-23 14:26 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
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 [this message]
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=db3e76a601cec0a42cf814d870206bd4@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 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.