Other terminal emulators are stricter about processing control sequences correctly, or do not yet implement sub-parameter support. Thus CSI 0 : 3 3 m is treated as SGR 0 and SGR 33.

Your outer terminal emulator is apparently one of the ones that handles sub-parameters with a bodge that treats them as parameters. Sub-parameters are separated by colon :, as specified in ITU-T T.416:1993 § 13.1.8. Parameters are separated by semi-colon, as specified in ECMA-48:1991 § 5.4.2. The problem is that you are using sub-parameters in your control sequence, not parameters. Whilst it is correct that you must always set the TERM environment variable to match your terminal type, and not blithely and erroneously assume that your terminal type is xterm-*, this is in fact nothing to do with the problem, as the TERM environment variable has no bearing upon literal control sequences embedded in your prompt. The prompt colors work in screen and in 'raw' bash outside of tmux, just not in tmux. Opening a new bash instance again within tmux doesn't make any difference - still no color.bash_profile is being read and $PS1 is being set. The fish shell has a color prompt inside tmux.

The following environment variables are exactly the same inside and outside of tmux: $ echo echo $TERMĬolor works perfectly for other commands inside tmux, like ls -la and git log.

The same version of bash running inside tmux and outside. Bash and tmux are the latest versions from the homebrew package manager. nf: set -g default-terminal 'xterm-256color' Outside of tmux I get a colored prompt reading a tmux session, the text is set but the prompt is not colorized.

Mac emulator codes not working