Black-on-black output from ansible-lint

[chriscroome]

The latest version of ansible-lint produces black-on-black output for warnings.

And as suggested here I have captured the output to a file and tested the result using less:

FORCE_COLOR=1 ansible-lint 2> /tmp/ansible-lint.txt
less -R /tmp/ansible-lint.txt

I have attached this output: ansible-lint.txt

It has been suggested that this is a client issue, I was wondering if anyone here has a view on this?

The code in question, \033[1;30m is listed here as bold black so it doesn't appear to me as if Kitty is doing anything wrong?

I have the following version of kitty and local config (I have put this at the end of the comment as it caused formatting issues when it was followed by further text):

kitty -v
kitty 0.39.0 created by Kovid Goyal

cat ~/.config/kitty/kitty.conf | grep -v ^\# | awk 'NF' -
font_size 9.0
map ctrl+shift+v send_text all \x16
scrollback_lines 16000
detect_urls no
focus_follows_mouse yes
enable_audio_bell no
enabled_layouts *
window_padding_width 4
shell bash --login
editor /usr/bin/vim
close_on_child_death yes
env HISTSIZE=9000
env HISTFILESIZE=9000
env LANG=en_GB.UTF-8
env LANGUAGE=en_GB.UTF-8
env ANSIBLE_COLOR_DEBUG=blue
env EDITOR=/usr/bin/vim
env PATH=${HOME}/bin:${HOME}/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
wayland_enable_ime no

[kovidgoyal]

I didnt look at the dump file but this is obviously a client issue. The terminal emulator simply uses whatever colors the client tells it too. One thing the client should make sure of is that it is not using bold to get bright colors, instead it needs to use colors from 8-15 for the bright versions of colors from 0-7.