Thomas Dickey dickey at
Sat Jun 5 19:39:34 UTC 2010

On Sat, Jun 05, 2010 at 10:13:34AM -0700, Chip Camden wrote:
> Thanks for your response, but I solved the problem by specifying that
> mutt should use slang instead of ncurses.  That works better in a couple
> of ways, so I'll go with that.
> I do, however, still have one small problem.  I can't seem to get mutt to
> see that my urxvt has 256 colors enabled.  infocmp shows "colors#256" for
> rxvt-256color, but if I do 'export TERM=rxvt-256color' then zsh complains
> "can't find terminal definition for rxvt-256color" (though it lets me set
> it anyway).  However, mutt still complains if I try to use any color
> above 8.  With TERM set to "rxvt" infocmp shows "colors#8" and tput
> colors shows "145".  I'm confused.  Obviously, not everyone is on the
> same page here.

There is more than one potential problem - here're a few:

ncurses' default configuration doesn't support 256 colors ("only" 16,
which was more than the standard 15 years ago).  It supports 256 colors
as a binary-incompatible extension of ncursesw, which could be provided
in a port.  With/without the extension, infocmp would show the 256.

zsh may be looking in the termcap interface, which iirc on FreeBSD is
using a separate database.

FreeBSD may still be using a tput that's not based on ncurses.
"145" is puzzling here, too.

Thomas E. Dickey
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
Url :

More information about the freebsd-questions mailing list