|
From: | Daniel Herring |
Subject: | TAP colors |
Date: | Thu, 26 Oct 2017 09:08:05 -0400 (EDT) |
User-agent: | Alpine 2.20 (DEB 67 2015-01-07) |
Hi,Regarding the topic of colored TAP output, it seems that there are good reasons for having both plain-text and colored-text output. There are also reasons for people to customize the colors.
Here are two ideas that might help. For all I know, the code may already be structured this way, and we just have a small documentation issue to improve awareness of the features.
1) Would it be hard to support both, perhaps with separate targets like tap and tap-color? Then people can easily select plain and colored text according to preference or present need.
2) Would it be possible to split out the color escape sequences into Autoconf site configuration variables? Named according to semantics, not the actual color, something like TAP_COLOR_PRE_WARN and TAP_COLOR_POST_WARN. Then you could provide configurations for dark ANSI background, light ANSI background, and people with non-ANSI terminals could do whatever their terminal requires.
Implementing #2 might also simplify #1. Plain text has empty escape sequences...
Later, Daniel
[Prev in Thread] | Current Thread | [Next in Thread] |