 |
|
| Linux Forum Index » Linux X » color9 - color14 on a 256-color xterm - ncurses.... |
|
Page 1 of 1 |
|
| Author |
Message |
| Chris Jones... |
 Posted: Mon Feb 09, 2009 1:49 pm |
|
|
|
Guest
|
I'm running an ncurses-based irc client called "weechat-curses" with the
TERM environment variable set to "xterm-256color".
I'm pretty sure everything involved on the ncurses/terminfo side is what
came with debian etch - the only thing I remember doing was compiling
xterm to enable 256-color support.
The irc client supports black+white and two tones of the usual colors
(red, green, yellow, blue, magenta, & cyan) and lets you specify that
you want, e.g. the currently active nicks, colored .. say .. "red",
"lightred", "green", and "lightgreen".
This syntax corresponds to xterm's color1, color9, color2, and color10.
The problem is that "red" and "lightred", "green" and "lightgreen" are
identical and correspond to the "non-bold" colors, IOW, the ones in the
top half of the 16-color palette when I run the 256color2.pl test script
that comes with xterm.
I first verified that this was not a problem with the weechat-curses
client by running it on the linux console. I also ran it in fbiterm
which is an emulator that runs on top of the linux console and is
256-color capable - no particular reason for these choices, it just
happens that they were the only other "terminals" that are installed on
this system.
In both cases the "light colors" were displayed correctly.
I proceeded to start the same 256-color capable xterm, which apparently
defaults to TERM=xterm and started the weechat app, and here again the
"light" colors were rendered correctly.
I would imagine the same X resources were active for both xterm/weechat
runs.. so I was wondering if this could be an issue with my terminfo
entry?
Thanks,
CJ |
|
|
| Back to top |
|
|
|
| dickey... |
| Posted: Thu Feb 19, 2009 3:58 pm |
|
|
|
Guest
|
On Feb 17, 8:35 pm, Chris Jones <cjns1... at (no spam) optimum.net> wrote:
(I didn't notice the yesterday)
Quote: Sorry I can't think of any other course of action at this point, but I
spent most of my "linux time" over the last week trying to figure out
what is causing this and I haven't made any progress whatsoever.
I can see the effect - am short of time right now (perhaps more
tomorrow).
You do have colorBDMode set (which tells it to display bold in color). |
|
|
| Back to top |
|
|
|
| Chris Jones... |
| Posted: Thu May 07, 2009 2:38 pm |
|
|
|
Guest
|
Quote: Chris Jones <cjns1989 at (no spam) optimum.net> wrote:
I'll check if unsetting TERMCAP (and possibly exporting an empty one)
prior to invoking alsamixer does the trick in my setup. If that work
then I would probably need to add that to my ~/.bashrc.
unset TERMCAP; export TERMCAP
... works around the issue.
Don't know why I don't have the problem with the versions I'm running on
debian "etch", though.
CJ |
|
|
| Back to top |
|
|
|
|
|
All times are GMT - 5 Hours
The time now is Tue Dec 01, 2009 9:12 am
|
|