Re: 256 colors
On Wed, Sep 06, 2006 at 08:05:24AM EDT, Alain Bench wrote:
> On Monday, September 4, 2006 at 17:09:58 -0400, cga2000 wrote:
[..]
> > the "use=" statements should reflect the order of the successive
> > layers in my "stack" .. IOW, the xterm being at the bottom, the
> > "use=screen-bce" should come before the "use=xterm" .. I'm still
> > unclear as to why this should not be.
> Because then the 8 colors definitions of screen would overrule the 256
> colors defs. Which is not the goal.
Found that by reversing the two entries.
> > tic replied with an "xterm+256color" terminfo not found
>
> Old terminfo database: Either upgrade, or tic this block first:
>
> | xterm+256color|Xterm-like 256 colors definitions,
> | colors#256, pairs#32767,
> | setab=\E[%?%p1%{8}%<%t4%p1%d%e%p1%{16}%<%t10%p1%{8}%-%d%e48;5;%p1%d%;m,
> | setaf=\E[%?%p1%{8}%<%t3%p1%d%e%p1%{16}%<%t9%p1%{8}%-%d%e38;5;%p1%d%;m,
> | setb@, setf@,
>
> > I had to change that to "use=xterm-256color" to match the actual
> > terminfo entry on my system.
>
> Not good: Those entries are completely different.
>
> > the "indicator" line in the index is "interrupted"
>
> And with a recreated proper screen-256color-bce?
Works right out of the box ..!!!
Fixes the broken status line problem .. _and_ 256 colors are now
available to mutt, vim, ELinks .. without any ugly config file hacks.
> > in my .screenrc:
> >| termcapinfo xterm 'Co#256:AB=\E[48;5;%dm:AF=\E[38;5;%dm'
> > would add 256-color capability to my plain xterm/screen-bce terminals.
> I'm not Screen expert, but I believe this overrules the given values
> of the xterm terminfo entry. So this forces 256c mode between Screen
> and Xterm. It does not change screen-bce entry, nor Screen's behaviour
> seen by apps inside. And it fails if the real terminal doesn't support
> 256 colors (older Xterms, other terms claiming compatibility, ASO).
> To me, this screenrc line seems a bad idea. Better use
> TERM=xterm-256color where appropriate.
I had no clue what I was doing but retrospectively that's probably what
happened .. To fix the "bce issue" I set TERM to terminfo entries that
were not 256-color capable on terminals (screen/xterm) that _did_ have
the capability .. and then used the config files where possible (vim,
eg.) to inform the apps of the terminal's real color capabilities ..
Just a thought, but shouldn't your new screen entry be "officially"
added to the terminfo database so that others benefit by your fixing
this annoying issue?
Thanks
cga