Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 17 Jan 2000 21:35:50 +0600 (NOVT)
From:      "Alexey N. Dokuchaev" <danfe@ssc.nsu.ru>
To:        Christian Weisgerber <naddy@mips.rhein-neckar.de>
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: No color in xterm
Message-ID:  <Pine.LNX.4.10.10001172133350.6550-100000@inet.ssc.nsu.ru>
In-Reply-To: <85sdg0$1h3o$1@bigeye.rhein-neckar.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On 16 Jan 2000, Christian Weisgerber wrote:

> John Indra <m4v3r1ck@bigfoot.com> wrote:
> 
> > I have Mutt 1.0i installed on my FreeBSD 3.4-RELEASE, compiled against
> > S-Lang 1.3.10. In consoles, Mutt shows color just fine, but when I run
> > Mutt on an xterm, it doesn't show color at all.
> 
> Presumably the program checks the termcap entry and doesn't find any
> indication of color support there. Try TERM=xterm-color.
> 
> > when I use gnuls --color=auto, xterm seems to render the color,
> 
> That blows out ANSI color control sequences without any regard
> whatsoever for the actual terminal type. xterm indeed renders those.
> (A different terminal might self-destruct. :-) )
> 

And, under Linux, midnight commander will display colors even with
TERM=vt100, that's no the case udner FreeBSD port of it.  Does anyone know
for sure that linux mc does not check for terminal type, and fBSD's midc
does?  Just don't want to dig into sources....

WBR,

./danfe




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.10.10001172133350.6550-100000>