Date: Tue, 22 Jul 1997 23:06:02 +1000 From: David Dawes <dawes@rf900.physics.usyd.edu.au> 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 Message-ID: <19970722230602.13588@rf900.physics.usyd.edu.au> In-Reply-To: <19970722111536.51938@wup.de>; from Andreas Klemm on Tue, Jul 22, 1997 at 11:15:36AM %2B0200 References: <19970722111536.51938@wup.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 22, 1997 at 11:15:36AM +0200, Andreas Klemm wrote: >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 ??? The most common reason for xterm colour not working with XFree86 releases prior to XFree86 3.3 is that the colour resources are set in the XTerm-color app-defaults file, not the one called XTerm. One solution is to put: *customization: -color in your ~/.Xdefaults file. Another is to put the colour resource settings from the XTerm-color app-defaults file into the XTerm app-defaults file. In XFree86 3.3, the default configuation is colour-friendly. (BTW, FreeBSD 2.2.2 ships with XFree86 3.2 as far as I know, not X11R6.2 -- and the xterm in the standard X11R6.x releases doesn't do colour anyway.) David
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970722230602.13588>