
This line checks if enviromental variable $TERM starts with st (therefore st*) and makes sure to use true color ( Tc) because current "indexed colors" (8 bits = 2^8 = 256 colors) is not enough for us. So I write like this: set-option -sa terminal-overrides ",st*:Tc" In configuration file ~/.nf I must now first make sure to identify enviromental variable TERM that my terminal set. Here you can't do anything but to remember this string. Somewhere in the binary there is a string literal that is set as a enviromental variable TERM when terminal is started. It is similar with whichever terminal you use.


Open a terminal (whichever you use - I use st) and write a command: ┌───┐Īs answer I got a string st-256color because this string is compiled as the C string literal termname in the st (check here). To me it looks like nobody knows what is talking about.
