Nicholas Marriott <nicholas.marri...@gmail.com>: > There are differences in how setaf is defined between xterm and > xterm-256color: > > $ TERM=xterm tput setaf 4|cat -v; echo > ^[[34m > $ TERM=xterm-256color tput setaf 4|cat -v; echo > ^[[38;5;4m > > So, when you do: > > $ printf '\e[1;34mabc' > > tmux sets colour 4 using setaf which with xterm-256color ends up as: > > ^[[1m^[[38;5;4mabc > > This means you get bold + colour 4. In the 256 colour palette, 4 is hardcoded > to ANSI blue. You've told xterm not to use a bold font, so it doesn't change > that, and there are no bold colours in the 256 colour palette, so you just get > colour 4, normal ANSI blue. > > I think what you want can be produced by making tmux use the standard escape > sequence for normal colours and only use the extended sequence (\e[38;5;n) for > the 256 colour palette. You can do this either by just using TERM=xterm and > starting the tmux server with -2 to force it to use 256 colours, or by
This seems to work... > overriding setaf and setab, something like: > > set -ag terminal-overrides ",xterm-256color:setaf=\e[3%p1%dm:setab=\E[4%p1%dm" ...while this one sadly doesn't. It actually completely breaks my output: zsh% printf '\e[38;5;12mfoo\n' foo <- That foo is actually in light blue, but: zsh% printf '\e[01;34mfoo\n' E[34mfoo zsh% Since I'm no expert in this terminfo business, that leaves me a little puzzled; especially, since I would prefer the $terminal-overrides solution. Regards, Frank ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
