Re: (no subject)

[ara.t.howard]

On Oct 9, 2007, at 11:22 AM, cga2000 wrote:

> IIRC .. you first need to have a version of screen that supports 256
> colors _and_ specify --enable-colors256 when you ./configure it prior
> to compile.

right.  the Portfile on OSX does indeed specify this option to configure

> Another thing is that you are going to need to have screen point to a
> terminfo entry that supports 256 colors.
>
> I do the latter with the following .screenrc statement:
>
>   term    "screen-256color-bce"

how odd, with that in my .screenrc i get the following error on startup:

"TERMCAP", line 20, col 1, terminal 'screen-256color-bce': Illegal  
character (expected alphanumeric or @%&*!#) - ^J


cfp:~ > cat .screenrc
termcapinfo xterm ti@:te@
defscrollback 4242            #Will be handled localy

### http://frexx.de/xterm-256-notes/
# terminfo and termcap for nice 256 color terminal
# allow bold colors - necessary for some reason
attrcolor b ".I"

# tell screen how to set colors. AB = background, AF=foreground

# erase background with current bg color
defbce "off"

term "screen-256color-bce"
termcapinfo xterm 'Co#256:AB=\E[48;5;%dm:AF=\E[38;5;%dm'


> Even if this turns out not to be necessary (?) to run your 256-color
> test from a shell successfully, you will need a correct terminfo entry
> for screen-mode apps that use it to determine the capabilities of the
> underlying terminal anyway (mutt, vim, eg.)

well i think that's okay since every works in straight iterm or  
terminal, it's only under screen where things be hosed.

cheers.

a @ http://codeforpeople.com/
--
it is not enough to be compassionate.  you must act.
h.h. the 14th dalai lama