On Wed, May 18, 2005 at 03:47:58PM -0700, Jeremy Chadwick wrote:
> Using TERM=xterm-256color does not fix it, as expected, as I believe
> the problem to be with screen and not the environment. :-)
>
> I'll repeat myself: using TERM=xterm works fine outside of screen,
> yadda yadda. I've even bothered to try some custom .screenrc hacks
> using termcapinfo, thinking some of the extra parameters need to be
> defined (AB=ESC[48;5;%dm and AF=ESC[38;5;%dm) -- doesn't fix it.
Does your termcap entry for xterm contain Co#256? That's how screen
detects if your terminal supports 256 colors. Maybe adding
termcapinfo xterm Co#256
does the trick for you. (Of course you might need AB/AF as well).
Note also that the xterm termcap entries that ship with the xterm
program contain:
# These aliases are for compatibility with the terminfo; termcap cannot provide
# the extra features, but termcap applications still want the names.
x1|xterm-16color|xterm alias:tc=xterm-xfree86:
x2|xterm-88color|xterm alias:tc=xterm-256color:
x3|xterm-256color|xterm alias:tc=xterm-xfree86:
xn|xterm-nrc|xterm alias:tc=xterm:
xr|xterm-rep|xterm alias:tc=xterm:
xx|xterm-xmc|xterm alias:sg#1:tc=xterm:
In other words, they don't support the color codes. But maybe your
termcap contains different entries.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
_______________________________________________
screen-users mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/screen-users
