From owner-freebsd-ports  Tue Jul 22 03:56:15 1997
Return-Path: <owner-freebsd-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id DAA21914
          for ports-outgoing; Tue, 22 Jul 1997 03:56:15 -0700 (PDT)
Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id DAA21909;
          Tue, 22 Jul 1997 03:56:08 -0700 (PDT)
Received: from ct.picker.com by whqvax.picker.com with SMTP;
          Tue, 22 Jul 1997 6:53:41 -0400 (EDT)
Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1)
	id AA13633; Tue, 22 Jul 97 06:53:34 EDT
Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4)
	id GAA25966; Tue, 22 Jul 1997 06:51:19 -0400
Message-Id: <19970722065118.42843@ct.picker.com>
Date: Tue, 22 Jul 1997 06:51:18 -0400
From: Randall Hopper <rhh@ct.picker.com>
To: andreas.klemm@wup.de, andreas@klemm.gtn.com
Cc: hackers@FreeBSD.ORG, ports@FreeBSD.ORG
Subject: Re: FBSD 2.2.2 - problem: no colors when using mutt in a color xterm
References: <19970722111536.51938@wup.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.76
In-Reply-To: <19970722111536.51938@wup.de>; from Andreas Klemm on Tue, Jul 22, 1997 at 11:15:36AM +0200
Sender: owner-freebsd-ports@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Andreas Klemm:
 |At home I'm using FreeBSD-current and X11R6.3. There it's possible, to get
 |mutt configured to use colors.
 |
 |I start xterm +xm -tn xterm-color, start mutt from within this
 |xterm session and get nice colors.
 |
 |When doing this on FreeBSD 2.2.2 using X11R6.2 (the FreeBSD version
 |shipped with 2.2.2), then I only get black and white display.
 |
 |Is some solor support not implemented in 2.2.2 ???

Yes, you have at least two options:

Option #1: 

     If compiled with either ncurses or Slang:

          setenv TERM xterm-color

     to activate a terminal entry that has the color-capability set.  

     This has the conn that the xterm-color entry isn't as well written as
     the xterm one, so some of your terminal emulation won't work as well.
     Read on...

Option #2: 

     If compiled with Slang, just use your regular "xterm" terminal entry
     (i.e. leave TERM set to "xterm") and:

        setenv COLORTERM y

I recommend compiling with Slang.  I've been running with it on FreeBSD and
Solaris for a good while now, doing color with both mutt and slrn (a news
reader).

Randall