Subject: Re: NETBSD vs. Linux 'ls' command
To: None <kenh@cmf.nrl.navy.mil, winter@jurai.net>
From: Max Bell <mbell@europa.com>
List: port-i386
Date: 02/03/1996 10:56:00
>From: Ken Hornstein <kenh@cmf.nrl.navy.mil>
>>On Thu, 1 Feb 1996, Ken Hornstein wrote:
>>> I'd like to point out that this feature of GNU ls is extremely evil.  Why?
>>> Because it assumes that ANSI color-setting codes work on the tty you're
>>> using.  If you happen to use a terminal that locks up when sent ANSI term
>>> escape sequences, this really really _really_ sucks.

>>Test for your terminal type in your .profile or .cshrc and set your 
>>ls alias with our without the color option depending on what your 
>>terminal type is.  Sheesh.

>Hey, _I_ don't have a problem doing this.  But making it the default for
>a system really bites.  That's what I was trying to say.

IMHO, it is best to avoid making any assumptions about user hardware when
setting up defaults.  The practice of hard-coding modem and network ttys
as vt100's is common enough that I treat it as unknown in my login scripts.
The VMS command "SET TERM/INQUIRE" is similarly evil -- non-VT class terminals
can lock up from the query sequence.

Max