Value | Color |
---|---|
\e[0;30m | Black |
\e[0;31m | Red |
\e[0;32m | Green |
\e[0;33m | Yellow |
\e[0;34m | Blue |
\e[0;35m | Purple |
\e[0;36m | Cyan |
\e[0;37m | White |
Value | Color |
---|---|
\e[1;30m | Black |
\e[1;31m | Red |
\e[1;32m | Green |
\e[1;33m | Yellow |
\e[1;34m | Blue |
\e[1;35m | Purple |
\e[1;36m | Cyan |
\e[1;37m | White |
Value | Color |
---|---|
\e[4;30m | Black |
\e[4;31m | Red |
\e[4;32m | Green |
\e[4;33m | Yellow |
\e[4;34m | Blue |
\e[4;35m | Purple |
\e[4;36m | Cyan |
\e[4;37m | White |
Value | Color |
---|---|
\e[40m | Black |
\e[41m | Red |
\e[42m | Green |
\e[43m | Yellow |
\e[44m | Blue |
\e[45m | Purple |
\e[46m | Cyan |
\e[47m | White |
Value | Color |
---|---|
\e[0;90m | Black |
\e[0;91m | Red |
\e[0;92m | Green |
\e[0;93m | Yellow |
\e[0;94m | Blue |
\e[0;95m | Purple |
\e[0;96m | Cyan |
\e[0;97m | White |
Value | Color |
---|---|
\e[1;90m | Black |
\e[1;91m | Red |
\e[1;92m | Green |
\e[1;93m | Yellow |
\e[1;94m | Blue |
\e[1;95m | Purple |
\e[1;96m | Cyan |
\e[1;97m | White |
Value | Color |
---|---|
\e[0;100m | Black |
\e[0;101m | Red |
\e[0;102m | Green |
\e[0;103m | Yellow |
\e[0;104m | Blue |
\e[0;105m | Purple |
\e[0;106m | Cyan |
\e[0;107m | White |
Value | Color |
---|---|
\e[0m | Reset |
Except in awk (as I discovered a short while ago) which is extensively used in Linux so it should fail only in numerous scenarios. \033 works perfectly cromulantly with both awk/nawk, as tested on RPi3B using the following 1-liner:
ifconfig | grep -E "(eth|wlan)[0-9]*\: |([0-9]{1,3}\.){3}[0-9]{1,3}" | grep -v 127.0.0.1 | awk 'BEGIN {ORS=" "} {gsub(/flags.*/, "", $2); gsub(/inet6?/, "", $1); print "\033[1;7m"$1"\033[0m" $2} END {printf "\n"}'