From owner-freebsd-current Tue Jan 14 18:29:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA28097 for current-outgoing; Tue, 14 Jan 1997 18:29:10 -0800 (PST) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA28091 for ; Tue, 14 Jan 1997 18:29:06 -0800 (PST) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.2/8.8.2) id NAA06768 for current@freebsd.org; Wed, 15 Jan 1997 13:29:03 +1100 (EST) From: David Dawes Message-Id: <199701150229.NAA06768@rf900.physics.usyd.edu.au> Subject: Re: a last word on last In-Reply-To: from J Wunsch at "Jan 15, 97 00:31:37 am" To: current@freebsd.org Date: Wed, 15 Jan 1997 13:29:03 +1100 (EST) X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >As Christoph Kukulies wrote: > >> BTW, is color_xterm gone from port/x11 now and is xterm >> the full replacement for this (as Satoshi (?) mentioned earlier)? > >The X11R6.1 (and higher) xterm supports ANSI color codes, i think this >was the reason why the color_xterm port went away. (I never used >color_xterm, but my xterm supports colors. ;) More correctly, the XFree86 3.2 and higher xterm supports ANSI colour codes. The X Consortium didn't pick up these changes, so they are not in their standard releases. Those who have problems getting things in colour when TERM is set to xterm-color, check that you have the XTerm-color app-defaults file installed, *and* that you have something like the following in your .Xdefaults file: #ifdef COLOR *customization: -color #endif so that it gets used. I think this is the most common reason for people having problems getting it to work. David