From owner-freebsd-stable Tue Jul 18 17:28:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.102.114]) by hub.freebsd.org (Postfix) with ESMTP id 9417B37B50B; Tue, 18 Jul 2000 17:28:26 -0700 (PDT) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.3/8.9.3) id RAA98236; Tue, 18 Jul 2000 17:28:25 -0700 (PDT) (envelope-from mph) Date: Tue, 18 Jul 2000 17:28:25 -0700 From: Matthew Hunt To: Mike Smith Cc: freebsd-stable@freebsd.org Subject: Re: Color ls Message-ID: <20000718172825.B98089@wopr.caltech.edu> References: <20000718171141.A97774@wopr.caltech.edu> <200007190031.RAA20235@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007190031.RAA20235@mass.osd.bsdi.com>; from msmith@freebsd.org on Tue, Jul 18, 2000 at 05:31:47PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 18, 2000 at 05:31:47PM -0700, Mike Smith wrote: > Yes. Any program that expects colour to work. In what sense? The color codes are absorbed by xterm and it looks like it probably does without doing color stuff. Do you know of a program which actually has problems? > The correct fix here is to tell your xterms to identify themselves as > xterm-color. This will then proceed to break anyone that wants to use an > xtern to talk to a system that doesn't know what xterm-color is. Yeah. Believe it or not, I log in to lots of random Suns and don't like having to reset TERM. > The more correct fix here is to stop worrying about fucking colourised ls > output and focus on the seventeen dozen more important things that need > your angst. I don't like colorized ls. I do like colorized mutt. But thanks for telling me what I should care about. Tell me what my proposed solution breaks, for real. -- Matthew Hunt * UNIX is a lever for the http://www.pobox.com/~mph/ * intellect. -J.R. Mashey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message