Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!shelby!csli!rustcat
From: rustcat@csli.Stanford.EDU (Vallury Prabhakar)
Newsgroups: alt.sources
Subject: Re: Path Program
Message-ID: <9430@csli.Stanford.EDU>
Date: 16 Jun 89 22:45:34 GMT
References: <2912@csd4.milw.wisc.edu> <KARL.89Jun14091306@giza.cis.ohio-state.edu> <702@censor.UUCP>
Sender: rustcat@csli.Stanford.EDU (Vallury Prabhakar)
Reply-To: rustcat@csli.stanford.edu (Vallury Prabhakar)
Distribution: na
Organization: Stanford University
Lines: 18

In article <702@censor.UUCP> markk@censor.UUCP (Mark Keating) writes:
% 
% path \- locate the executable for a command

[...]

% will report on the location of
% .I file,
% searching every directory in the path (as defined in the
% $PATH variable), much like the operating system does when searching
% $PATH to execute a program.  It is handy for finding out where in your path
% a command resides. 

[...Source code deleted...]


Is this in any way better or different from the `which' command on BSD 
systems?  Just curious.