From owner-freebsd-stable Tue Jul 18 17:35:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 4350037BC4F for ; Tue, 18 Jul 2000 17:35:42 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id RAA20342; Tue, 18 Jul 2000 17:44:29 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007190044.RAA20342@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Hunt Cc: freebsd-stable@freebsd.org Subject: Re: Color ls In-reply-to: Your message of "Tue, 18 Jul 2000 17:28:25 PDT." <20000718172825.B98089@wopr.caltech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Jul 2000 17:44:29 -0700 From: Mike Smith 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? I can think of dozens. Try anything that depends on colour to identify eg. menu selections. > > 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. So fix your Sun systems so that they recognise xterm-color. > > 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. The xterm terminal definition does not support colour. It is an error to corrupt our terminal capabilities database such that we use the xterm-color definitions for a terminal identifying itself as 'xterm'. If you want Mutt to work, set your terminal type correctly. If you have to access a broken remote host, fix your exported terminal type correctly. You are attempting to rationalise "wrong" behaviour, and that's just plain "wrong". -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message