color problem
Atom 'Smasher'
in pine i can force the display to use 16 colors and i have a lot of things
using those colors.
in mutt, i seem to have 16 colors but not the way i want them... i seem to
have 8 "normal" colors and another 8 "bright" colors.
example line from my ~/.muttrc is this:
color indicator brightyellow yellow
which produces this:
http://atom.smasher.org/tmp/mutt-color.png
"brightyellow" is not only *bold*, but it's a different color than "yellow",
despite what the DOCs say:
foreground can optionally be prefixed with the keyword bright to
make the foreground color boldfaced (e.g., brightred).
anyway... how can i get the "brightyellow" color (and other *bright* colors)
without the bold? the same thing happens with all of the colors... bright*
makes it bold AND changes the color. i want to get the brighter colors
(which i find easier to read) but not bold (which i find makes it harder to
read).
this shot:
http://atom.smasher.org/tmp/color.png
shows the colors that i *should* have.
i've tried setting TERM to different values and setting/unsetting COLORTERM
and i keep getting the same results.
i've also tried colorX but any "X" > 7 causes a notice on startup that the
color is not supported.
this is Mutt 1.4.2.1i
Ben Finney
> anyway... how can i get the "brightyellow" color (and other *bright*
> colors) without the bold?
This is a feature of your terminal; Mutt is not specifying any bolding
(it doesn't know how). Investigate your X terminal program's features
to see how to disable bold for bright colours.
--
\ "I was in the first submarine. Instead of a periscope, they had |
`\ a kaleidoscope. 'We're surrounded.'" -- Steven Wright |
_o__) |
Ben Finney <http://bignose.squidly.org/>
Atom 'Smasher'
> (it doesn't know how). Investigate your X terminal program's features
> to see how to disable bold for bright colours.
>
http://atom.smasher.org/tmp/color2.png
in the shot above, you can see that BOLD and BRIGHT are dealt with as
distinctly different things by my terminal(s).
~something~ is telling my terminal to display the the text as both bold and
bright. what is it and how do i turn it off?
thanks...
Ben Finney
> http://atom.smasher.org/tmp/color2.png
>
> in the shot above, you can see that BOLD and BRIGHT are dealt with as
> distinctly different things by my terminal(s).
So how did you get your terminal to produce that image?
> ~something~ is telling my terminal to display the the text as both
> bold and bright. what is it and how do i turn it off?
It may be a feature of ncurses; most full-screen console apps use that
library for painting the console.
--
\ "I put contact lenses in my dog's eyes. They had little |
`\ pictures of cats on them. Then I took one out and he ran around |
_o__) in circles." -- Steven Wright |
Ben Finney <http://bignose.squidly.org/>
Atom 'Smasher'
>>
>> in the shot above, you can see that BOLD and BRIGHT are dealt with as
>> distinctly different things by my terminal(s).
>
> So how did you get your terminal to produce that image?
http://atom.smasher.org/tmp/colors.gz
`cat colors`
>> ~something~ is telling my terminal to display the the text as both
>> bold and bright. what is it and how do i turn it off?
>
> It may be a feature of ncurses; most full-screen console apps use that
> library for painting the console.
===============================
hehe... a "feature" indeed...
would it be a bad idea to compile with slang instead? would that make a
difference?
Ben Finney
> Ben Finney wrote:
>> Atom wrote:
>>> ~something~ is telling my terminal to display the the text as both
>>> bold and bright. what is it and how do i turn it off?
>> It may be a feature of ncurses; most full-screen console apps use
>> that library for painting the console.
>
> a difference?
You have the source to Mutt available, and you are in a position to
determine whether compiling with a different library gives the result
you want. Please feel free to try it out!
--
\ "Sunday: A day given over by Americans to wishing that they |
`\ themselves were dead and in Heaven, and that their neighbors |
_o__) were dead and in Hell." -- Henry L. Mencken |
Ben Finney <http://bignose.squidly.org/>
Atom 'Smasher'
>> a difference?
>
> You have the source to Mutt available, and you are in a position to
> determine whether compiling with a different library gives the result
> you want. Please feel free to try it out!
apparently it makes no difference.
and yes, it did compile correctly. where strings in the binary previously
had "libncurses.so" it now has "libslang.so.1".
i still get bold [and bright] text when i specify bright, and i still get
"color not supported by term" when i try colorX > 7.
since both libraries produce the same (unintended) results, and i know my
terminal can produce bright AND/OR bold text, i'm starting to think the
problem is in mutt.
now what?
i don't consider myself a C programmer, but i guess i'll start poking around
in the mutt code....
Sven Guckes
> now what?
terminal name + version
program name + version
liberary name + version
screen+ssh? XFree?
$TERM $TERMCAP
etc etc
mutt understands 256 colors - with a patch.
$TERM must be correct and $TREMCAP, too.
screen might get in your way, too.
and.. lots of programs and problems.
one of these days i'll write abook about it.
that is, if i *ever* understand it all.. :-/
Sven