| commit | ee7297d4fb8467d5dd08e695bdd60a242ce94079 | |
| author | Kyle J. McKay <mackyle@gmail.com> | |
| Sat, 31 Dec 2016 18:57:36 +0000 (31 10:57 -0800) | ||
| committer | Kyle J. McKay <mackyle@gmail.com> | |
| Sat, 31 Dec 2016 18:57:36 +0000 (31 10:57 -0800) | ||
| tree | 85f6baee22acb5ecc9134d87c71b20fbd4098918 | treesnapshot (tar.gz zip) |
| parent | ac089b101e0cba89e296feed75abf821aa815c2b | commitdiff |
test-lib-main.sh: let --color enable color output
With all TAP output handled by say_tap and say_color_tap
with automatic color removal when `test -n "$HARNESS_ACTIVE"`
there's no reason not to provide a `--color` option to
enable color output to go with the pre-existing `--no-color`
option that disables it.
Therefore provide `--color` as an option. When HARNESS_ACTIVE
is non-empty color is ALWAYS suppressed for TAP lines so
it's safe to use `--color` with a TAP harness.
Signed-off-by: Kyle J. McKay <mackyle@gmail.com>
With all TAP output handled by say_tap and say_color_tap
with automatic color removal when `test -n "$HARNESS_ACTIVE"`
there's no reason not to provide a `--color` option to
enable color output to go with the pre-existing `--no-color`
option that disables it.
Therefore provide `--color` as an option. When HARNESS_ACTIVE
is non-empty color is ALWAYS suppressed for TAP lines so
it's safe to use `--color` with a TAP harness.
Signed-off-by: Kyle J. McKay <mackyle@gmail.com>
| t/test-lib-main.sh | diffblobblamehistory |