Re: 256 colors - xterm, screen, slrn

* cga2000 on Friday, October 26, 2007 at 19:03:11 -0400
> I tried "unset $TERMCAP" where it should have been "unset -v TERMCAP".
> 
> I did the latter just after I came home tonight and the script displayed
> all the pretty colors I was expecting.
> 
> Now I just have to find out for what purpose screen (presumably)
> initializes this variable and whether I can safely unset it  --

I'm trying this as well, and seems to work for a terminfo based
system.

I also tried:

terminfo xterm-256color "Co#256:pa#32767" "Co#256:pa#32767"

in screenrc, but this didn't have the desired effect; which is a
pity, as I /have/ to do:

term "screen-256color"

in screenrc for screenrc-keybindings like

bind V screen 4 vim

not to fallback on the simple "screen" $TERM value.
Unfortunately

$ infocmp screen-256color > screen-256color.src
$ infotocap screen-256color.src > ~/.screencap

and then, in bashrc:

export SCREENCAP=~/.screencap
[ -n "$STY" ] && export TERM="screen-256color"

doesn't work with the bindings either.

> and then find the proper way to do this without messing up
> everything.

Quite problematic according to my investigations; my dirty
workaround ATM:

bashrc:
if [ -n "$STY" ]
    unset TERMCAP
    export TERMCAP
fi

screenrc:
term "xterm-256color"
bind S screen -t slrn 1 bash -l -c slrn
#                       ^^^^^^^ force login

If someone has this working in a more elegant way, I'd be curious
to know about it.

c
-- 
__   _    _         _  __  _               _    
\ \ | |__| |__ _ __| |_\ \| |_ _ _ __ _ __| |_  
 \ \| '_ \ / _` / _| / /\ \  _| '_/ _` (_-< ' \ 
  \_\_.__/_\__,_\__|_\_\ \_\__|_| \__,_/__/_||_|   http://www.blacktrash.org/

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/