Isn't it true that ANSI sequences can vary depending on the terminal emulator? Does this program account for that somehow?
In my shell scripts I often use `tput bold` etc instead of hardcoding the sequences.
replies(2):
In my shell scripts I often use `tput bold` etc instead of hardcoding the sequences.
Yes, historically, many terminals were not even ANSI compatible. That is why the terminfo database (and its predecessor termcap) exist; for programs to look at the TERM environment variable, use that to look up the terminal’s capabilities in terminfo, and see what the terminal can and cannot do, and then choose to output whatever sequences the terminal does support. Normally, a program uses yet another library, like ncurses, to do this, but you can do it yourself if you want to, like in a shell script or similar. Outputting raw escape codes is wrong, since the correct way is so very easy.
On the other hand, ignoring ancient terminals and simply pretending everything is color-enabled, VT-220 compatible, UTF-8 aware terminal emulator works well enough™ almost everywhere, including recent versions of Windows (which IIRC don't even have terminfo; not that it'd help since the legacy Windows console uses ioctl()-like interface instead of the escape sequences) — and is actually easy.
I.e. I would expect
python3 -c 'print("\N{GREEK SMALL LETTER BETA}")'