Thomas Glanzmann

Hi,

> hmm - no. ncurses and slang are equivalent in their capabilities
> here. For ncurses, it is activated by function calls, e.g.,
> use_default_colors.

I didn't dive that deep into ncurses / slang to know, but it makes
sense of course.

> You're either describing a difference in the way mutt is coded, or
> some other configuration issue. Just checking, for example (with lynx
> where those aren't a factor, I see the so-called transparency, while
> Debian's mutt 1.5.4i with libncursesw doesn't).

If I use a ncurses enabled mutt. He doesn't know about the 'default' -
color I described earlier in that thread, while a slang enabled mutt
does. So I never really cared.

> Looking a little further (compiling 1.5.6 myself), I do indeed get the
> transparency. Perhaps you should file a bug report against the
> appropriate package - whatever problem is actually there isn't in the
> original sources.

Was it possible for you to get the transparency with ncurses and mutt?
If this is true for you, how?

When I compile mutt from cvs against the most recent version of ncurses.
I get the following errors on startup and after that I have default
colors for the 'default' stuff:

(faui03) [~/work/mutt/mutt] ./mutt
Error in /home/cip/adm/sithglan/.mutt/colors, line 2: default: no such color
....
Error in /home/cip/adm/sithglan/.mutt/colors, line 25: default: no such color
Error in /home/cip/adm/sithglan/.muttrc, line 10: source: errors in /home/cip/adm/sithglan/.mutt/colors
source: errors in /home/cip/adm/sithglan/.muttrc

However I will bring this to mutt-dev.

Thomas