Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #84701 > unrolled thread

Bug#1088739: colors make ip's output unreadable

Started byHarald Dunkel <harri@afaics.de>
First post2024-11-30 11:00 +0100
Last post2025-04-06 21:20 +0200
Articles 5 on this page of 25 — 12 participants

Back to article view | Back to linux.debian.kernel


Contents

  Bug#1088739: colors make ip's output unreadable Harald Dunkel <harri@afaics.de> - 2024-11-30 11:00 +0100
    Bug#1088739: colors make ip's output unreadable Luca Boccassi <luca.boccassi@gmail.com> - 2024-11-30 12:50 +0100
      Re: Bug#1088739: colors make ip's output unreadable Harald Dunkel <harald.dunkel@aixigo.com> - 2024-12-02 12:20 +0100
        Re: Re: Bug#1088739: colors make ip's output unreadable Luca Boccassi <bluca@debian.org> - 2024-12-03 20:30 +0100
          Re: Bug#1088739: colors make ip's output unreadable Bjørn Mork <bjorn@mork.no> - 2024-12-03 21:00 +0100
      Re: Bug#1088739: colors make ip's output unreadable Harald Dunkel <harald.dunkel@aixigo.com> - 2024-12-02 12:40 +0100
      Bug#1088739: colors make ip's output unreadable Bastian Blank <waldi@debian.org> - 2024-12-21 15:50 +0100
        Bug#1088739: colors make ip's output unreadable Bastian Blank <waldi@debian.org> - 2025-01-02 11:20 +0100
        Bug#1088739: colors make ip's output unreadable Luca Boccassi <bluca@debian.org> - 2025-01-02 21:00 +0100
    Processed: Re: colors make ip's output unreadable "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-11-30 12:50 +0100
    Re: Bug#1088739: colors make ip's output unreadable Bjørn Mork <bjorn@mork.no> - 2024-11-30 14:50 +0100
    Processed: Re: Bug#1088739: colors make ip's output unreadable "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-12-21 15:50 +0100
    Processed: Re: Bug#1088739: colors make ip's output unreadable "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-01-02 21:00 +0100
    Bug#1088739: colors make ip's output unreadable Axel Scheepers <axel.scheepers76@gmail.com> - 2025-01-12 13:30 +0100
    Bug#1088739: colors make ip's output unreadable Harald Dunkel <harri@afaics.de> - 2025-03-18 09:20 +0100
    Bug#1088739: colors make ip's output unreadable "Oliver M. Schode" <oliver.schode@online.de> - 2025-03-19 14:10 +0100
      Bug#1088739: colors make ip's output unreadable Ben Hutchings <ben@decadent.org.uk> - 2025-03-26 17:10 +0100
        Bug#1088739: colors make ip's output unreadable Luca Boccassi <bluca@debian.org> - 2025-03-26 19:00 +0100
    Bug#1088739: [PATCH iproute2 1/2] color: Introduce and use default_color_opt() function Ben Hutchings <benh@debian.org> - 2025-03-19 23:00 +0100
      Bug#1088739: [PATCH iproute2 2/2] color: Handle NO_COLOR environment variable in default_color_opt() Ben Hutchings <benh@debian.org> - 2025-03-19 23:00 +0100
    Bug#1088739: [PATCH iproute2 0/2] Improve coloured text readability Ben Hutchings <benh@debian.org> - 2025-03-26 15:10 +0100
      Bug#1088739: [PATCH iproute2 2/2] color: Do not use dark blue in dark-background palette Ben Hutchings <benh@debian.org> - 2025-03-26 15:20 +0100
      Bug#1088739: [PATCH iproute2 1/2] color: Assume background is dark if unknown Ben Hutchings <benh@debian.org> - 2025-03-26 15:20 +0100
      Bug#1088739: [PATCH iproute2 0/2] Improve coloured text readability patchwork-bot+netdevbpf@kernel.org - 2025-04-06 19:20 +0200
    Bug#1088739: marked as done (colors make ip's output unreadable) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-04-06 21:20 +0200

Page 2 of 2 — ← Prev page 1 [2]


#86617 — Bug#1088739: [PATCH iproute2 0/2] Improve coloured text readability

FromBen Hutchings <benh@debian.org>
Date2025-03-26 15:10 +0100
SubjectBug#1088739: [PATCH iproute2 0/2] Improve coloured text readability
Message-ID<KuzCa-8RJZ-1@gated-at.bofh.it>
In reply to#84701

[Multipart message — attachments visible in raw view] — view raw

Currently coloured text output isn't very readable in GNOME Terminal
or xterm with a dark background:

- These terminals don't set $COLORFGBG, so we end up using the
  light-background palette.

- The standard (dark) blue is also too close to black in their default
  dark palettes.

Ben.

Ben Hutchings (2):
  color: Assume background is dark if unknown
  color: Do not use dark blue in dark-background palette

 lib/color.c | 20 ++++++++++++--------
 1 file changed, 12 insertions(+), 8 deletions(-)

[toc] | [prev] | [next] | [standalone]


#86618 — Bug#1088739: [PATCH iproute2 2/2] color: Do not use dark blue in dark-background palette

FromBen Hutchings <benh@debian.org>
Date2025-03-26 15:20 +0100
SubjectBug#1088739: [PATCH iproute2 2/2] color: Do not use dark blue in dark-background palette
Message-ID<KuzLP-8RNI-1@gated-at.bofh.it>
In reply to#86617

[Multipart message — attachments visible in raw view] — view raw

In GNOME Terminal's default dark colour schemes, the default (dark)
blue on a black background is barely readable.  Light blue is
significantly more readable to me, and is also easily readable on a
white background.

In Konsole, rxvt, and xterm, I can see little if any difference
between dark and light blue in the default dark colour schemes.

So replace dark blue with light blue in the dark-background palette.

Signed-off-by: Ben Hutchings <benh@debian.org>
---
 lib/color.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/lib/color.c b/lib/color.c
index 88ba9b03..aa112352 100644
--- a/lib/color.c
+++ b/lib/color.c
@@ -24,7 +24,7 @@ enum color {
 	C_BOLD_RED,
 	C_BOLD_GREEN,
 	C_BOLD_YELLOW,
-	C_BOLD_BLUE,
+	C_BOLD_LIGHT_BLUE,
 	C_BOLD_MAGENTA,
 	C_BOLD_CYAN,
 	C_BOLD_WHITE,
@@ -42,7 +42,7 @@ static const char * const color_codes[] = {
 	"\e[1;31m",
 	"\e[1;32m",
 	"\e[1;33m",
-	"\e[1;34m",
+	"\e[1;94m",
 	"\e[1;35m",
 	"\e[1;36m",
 	"\e[1;37m",
@@ -66,7 +66,7 @@ static enum color attr_colors_dark[] = {
 	C_BOLD_CYAN,
 	C_BOLD_YELLOW,
 	C_BOLD_MAGENTA,
-	C_BOLD_BLUE,
+	C_BOLD_LIGHT_BLUE,
 	C_BOLD_GREEN,
 	C_BOLD_RED,
 	C_CLEAR

[toc] | [prev] | [next] | [standalone]


#86619 — Bug#1088739: [PATCH iproute2 1/2] color: Assume background is dark if unknown

FromBen Hutchings <benh@debian.org>
Date2025-03-26 15:20 +0100
SubjectBug#1088739: [PATCH iproute2 1/2] color: Assume background is dark if unknown
Message-ID<KuzLP-8RNI-5@gated-at.bofh.it>
In reply to#86617

[Multipart message — attachments visible in raw view] — view raw

We rely on the COLORFGBG environment variable to tell us whether the
background is dark.  This variable is set by Konsole and rxvt but not
by GNOME Terminal or xterm.  This means we use the wrong set of
colours when GNOME Terminal or xterm is configured with a dark
background.

It appears to me that the dark-background colour palette works better
on a light background than vice versa.  So it is better to assume a
dark background if we cannot find this out from $COLORFGBG.

- Change the initial value of is_dark_bg to 1.
- In set_color_palette(). conditinally set is_dark_bg to 0 with an
  inverted test of the colour.

Signed-off-by: Ben Hutchings <benh@debian.org>
---
 lib/color.c | 14 +++++++++-----
 1 file changed, 9 insertions(+), 5 deletions(-)

diff --git a/lib/color.c b/lib/color.c
index 3c6db08d..88ba9b03 100644
--- a/lib/color.c
+++ b/lib/color.c
@@ -72,7 +72,11 @@ static enum color attr_colors_dark[] = {
 	C_CLEAR
 };
 
-static int is_dark_bg;
+/*
+ * Assume dark background until we know otherwise. The dark-background
+ * colours work better on a light background than vice versa.
+ */
+static int is_dark_bg = 1;
 static int color_is_enabled;
 
 static void enable_color(void)
@@ -138,12 +142,12 @@ 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 this value is 0-6 or 8, background is dark; otherwise it's 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] >= '0' && p[1] <= '6') || p[1] == '8')
+		     && p[2] == '\0'))
+		is_dark_bg = 0;
 }
 
 __attribute__((format(printf, 3, 4)))

[toc] | [prev] | [next] | [standalone]


#86752 — Bug#1088739: [PATCH iproute2 0/2] Improve coloured text readability

Frompatchwork-bot+netdevbpf@kernel.org
Date2025-04-06 19:20 +0200
SubjectBug#1088739: [PATCH iproute2 0/2] Improve coloured text readability
Message-ID<KyBP3-bAHB-3@gated-at.bofh.it>
In reply to#86617
Hello:

This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:

On Wed, 26 Mar 2025 15:07:49 +0100 you wrote:
> Currently coloured text output isn't very readable in GNOME Terminal
> or xterm with a dark background:
> 
> - These terminals don't set $COLORFGBG, so we end up using the
>   light-background palette.
> 
> - The standard (dark) blue is also too close to black in their default
>   dark palettes.
> 
> [...]

Here is the summary with links:
  - [iproute2,1/2] color: Assume background is dark if unknown
    https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=cc0f1109d286
  - [iproute2,2/2] color: Do not use dark blue in dark-background palette
    https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=46a4659313c2

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html

[toc] | [prev] | [next] | [standalone]


#86759 — Bug#1088739: marked as done (colors make ip's output unreadable)

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2025-04-06 21:20 +0200
SubjectBug#1088739: marked as done (colors make ip's output unreadable)
Message-ID<KyDHc-bC4V-19@gated-at.bofh.it>
In reply to#84701

[Multipart message — attachments visible in raw view] — view raw

Your message dated Sun, 06 Apr 2025 19:09:52 +0000
with message-id <E1u1VNQ-00Ep2i-8s@fasolo.debian.org>
and subject line Bug#1088739: fixed in iproute2 6.14.0-2
has caused the Debian Bug report #1088739,
regarding colors make ip's output unreadable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1088739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088739
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]


Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | linux.debian.kernel


csiph-web