Re: 256 colors
On Monday, September 4, 2006 at 17:09:58 -0400, cga2000 wrote:
> On Thu, Aug 31, 2006 at 08:50:25AM EDT, Alain Bench wrote:
>> Reverse: Values declared first win.
> 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.
> 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?
> 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.
> does anyone who sticks with 8/16 colors in this day and age deserve
> our "pity".. ? :-)
Of course not, they're damn loosers, but... Depending on terminal
settings, this bright keyword doing bold/blink dark problem may also
affect our shiny 256 color mode. Do you sympathize on them, now? ;-)
Bye! Alain.
--
Mutt muttrc tip to send mails in best adapted first necessary and sufficient
charset (version for Western Latin-1/Latin-9/CP-850/CP-1252 terminal users):
set send_charset="us-ascii:iso-8859-1:iso-8859-15:windows-1252:utf-8"