[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240529111122.7d384ed9@hermes.local>
Date: Wed, 29 May 2024 11:11:22 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Edward Cree <ecree.xilinx@...il.com>
Cc: Gedalya <gedalya@...alya.net>, David Ahern <dsahern@...nel.org>,
netdev@...r.kernel.org
Subject: Re: [PATCH v3] iproute2: color: default to dark background
On Wed, 29 May 2024 18:51:01 +0100
Edward Cree <ecree.xilinx@...il.com> wrote:
> On 29/05/2024 17:36, Gedalya wrote:
> > That's not possible.
>
> Then in cases where the tool can't determine the answer, it
> should not be using colour at all unless explicitly instructed
> to do so, either on the command-line or in runtime
> configuration like dotfiles, /etc, or envvars.
> "In the face of ambiguity, refuse the temptation to guess."[1]
>
> > The fact remains that the code currently makes an
> > assumption and I don't see why it is better than
> > the other way around.
>
> Because changing it would break it for people for whom it
> currently works. That's a regression, and regressions are
> worse than existing bugs, ceteris paribus.
> "Assess[ing] what is more common" won't change that.
>
> -ed
>
> [1]: https://peps.python.org/pep-0020/#the-zen-of-python
>
Debian maintainer decided to enable color by changing source.
Therefore, they should carry whatever color fixups they want as well.
Upstream will stay as default no color.
Powered by blists - more mailing lists