Path: utzoo!utgpu!watserv1!watmath!att!linac!uwm.edu!wuarchive!uunet!auspex!guy
From: guy@auspex.auspex.com (Guy Harris)
Newsgroups: comp.bugs.sys5
Subject: Re: small bug in who(1) of SVR3
Message-ID: <5206@auspex.auspex.com>
Date: 12 Jan 91 19:39:42 GMT
References: <1991Jan10.130738.10194@unhtel.uucp> <14818@smoke.brl.mil> <4554@lib.tmc.edu>
Organization: Auspex Systems, Santa Clara
Lines: 12

>(Why does Berzerkeley ls have to act the way it does? Yuk. Having to say ls
>if the destination is a terminal, but ls -C if I want to pipe into, say,
>is nonintuitive at best.)

And since this is "comp.bugs.sys5", I note that S5R4's "ls" acts the way
the BSD one does; having people add aliases/shell functions to force
"-C" on, or wrapping a script around it with a different name to force
"-C" on, or having it look at "argv[0]" and force "-C" on if invoked
with the right name, might have been better.  And when I say "force", I
mean *FORCE*.  There are times when I want a multi-column listing when
"ls" is *not* going directly to the terminal, e.g. when piping it to a
pager program.