From: Stephen Hemminger <stephen@networkplumber.org>
To: Gedalya Nie <gedalya@gedalya.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] iproute2: color: default to dark background
Date: Wed, 22 May 2024 13:59:14 -0700 [thread overview]
Message-ID: <20240522135914.4dd914dc@hermes.local> (raw)
In-Reply-To: <01a20e83-c05e-4006-b64c-3edd34508296@gedalya.net>
On Thu, 23 May 2024 03:28:16 +0800
Gedalya Nie <gedalya@gedalya.net> wrote:
> Signed-off-by: Gedalya Nie <gedalya@gedalya.net>
> ---
> lib/color.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/lib/color.c b/lib/color.c
> index cd0f9f75..6692f9c1 100644
> --- a/lib/color.c
> +++ b/lib/color.c
> @@ -72,7 +72,7 @@ static enum color attr_colors_dark[] = {
> C_CLEAR
> };
> -static int is_dark_bg;
> +static int is_dark_bg = 1;
> static int color_is_enabled;
> static void enable_color(void)
> @@ -127,11 +127,11 @@ static void set_color_palette(void)
> * COLORFGBG environment variable usually contains either two or three
> * values separated by semicolons; we want the last value in either case.
> * If this value is 0-6 or 8, background is dark.
> + * If it is 7, 9 or greater, background is light.
> */
> if (p && (p = strrchr(p, ';')) != NULL
> - && ((p[1] >= '0' && p[1] <= '6') || p[1] == '8')
> - && p[2] == '\0')
> - is_dark_bg = 1;
> + && (p[1] == '7' || p[1] == '9' || p[2] != '\0'))
> + is_dark_bg = 0;
> }
> __attribute__((format(printf, 3, 4)))
>
You mailer mangled this.
WARNING: Missing commit description - Add an appropriate one
ERROR: patch seems to be corrupt (line wrapped?)
#115: FILE: lib/color.c:71:
C_CLEAR
total: 1 errors, 1 warnings, 25 lines checked
prev parent reply other threads:[~2024-05-22 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 19:28 [PATCH] iproute2: color: default to dark background Gedalya Nie
2024-05-22 20:59 ` Stephen Hemminger [this message]
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=20240522135914.4dd914dc@hermes.local \
--to=stephen@networkplumber.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