[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: how to determine startvalue for init_color

From: Thomas Dickey
Subject: Re: how to determine startvalue for init_color
Date: Sat, 28 Jan 2006 20:41:10 -0500 (EST)

On Sun, 29 Jan 2006, Folkert van Heusden wrote:

Am I right that 'init_color' isn't supported on any terminal at all
no.  It should be usable on the terminals that have the initc property.
I've tested it on Linux console (linux-c-nc) and with xterm compiled for
88- and 256-colors (xterm-256color).  I see that putty also supports this,
but I don't recall testing it.

Hmmm. If the terminal-program supports it, is it possible that it still
can't do it because of a compilation-setting in ncurses?

I tested these terminal programs:
ii  aterm                         0.4.2-11                 Afterstep XVT - a 
VT102 emulator for the X w
ii  eterm                         0.9.2-8.1                Enlightened Terminal 
ii  gnome-terminal                2.12.0-2                 The GNOME 2 terminal 
emulator application
ii  konsole                       3.3.2-1sarge1            KDE X terminal 
ii  mrxvt                         0.4.2-1                  lightweight 
multi-tabbed X terminal emulator
ii  multi-aterm                   0.2.1-1                  tabbed terminal 
emulator with efficent pseud
ii  multi-gnome-terminal          1.6.2-11.1               Enhanced the GNOME 
ii  pterm                         0.58-3                   PuTTY terminal 
ii  xterm                         208-3.1                  X terminal emulator
and none of them gave that I could change the colors and more then 8 colors.

It's defined in the terminfo.  The names I cited above are terminfo entry
names.  Normally ncurses supports 16 colors (256 pairs).  ncurses 5.5 can
be compiled to support 256 colors, but that's not binary-compatible with
the normal release, so it's experimental.

Of course you can set $TERM to any of those, but it doesn't mean that the
terminal supports those features...

Thomas E. Dickey

reply via email to

[Prev in Thread] Current Thread [Next in Thread]