Subject: Re: /usr/bin/which is a csh script!!?!
To: NetBSD-current Discussion List <current-users@netbsd.org>
From: Andrew Brown <atatat@atatdot.net>
List: current-users
Date: 04/30/2003 09:27:14
afiact, basically what it comes down to is:
(1) everyone uses a shell (if you don't, you don't count)
(2) everyone wants to know where a given command is (if you don't, you
don't count)
(3) most shells have such a built in function (or functions) already
(4) if you've used your shell for any period of time, you've probably
found it, and it probably also handles aliases properly
(5) if you're not using a shell smart enough to figure where something
is by itself (or if it doesn't provide aliases), the implementation of
which(1) as a csh script is probably perfectly acceptable to you
imho, the real bug is shells that provide aliases but don't provide
something like which(1) as a builtin, which is the only really wrong
case (shells that provide aliases and will only tell you that
something is an alias aside). which shells are the broken ones?
--
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org * "ah! i see you have the internet
twofsonet@graffiti.com (Andrew Brown) that goes *ping*!"
werdna@squooshy.com * "information is power -- share the wealth."