From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from relay1.UU.NET ([192.48.96.5]) by hawkwind.utcs.toronto.edu with SMTP id <2789>; Wed, 10 Mar 1993 18:32:21 -0500
Received: from uunet.uu.net (via LOCALHOST.UU.NET) by relay1.UU.NET with SMTP 
	(5.61/UUNET-internet-primary) id AA18112; Wed, 10 Mar 93 17:54:14 -0500
Received: from srg.UUCP by uunet.uu.net with UUCP/RMAIL
	(queueing-rmail) id 175344.4740; Wed, 10 Mar 1993 17:53:44 EST
Received: from ceres.srg.af.mil by srg.srg.af.mil
	id aa11947; Wed, 10 Mar 93 17:16:19 EST
From:	culliton@srg.srg.af.mil (Tom Culliton x2278)
X-Mailer: SCO System V Mail (version 3.2)
To:	cks@hawkwind.utcs.toronto.edu, rc@hawkwind.utcs.toronto.edu
Subject: Re: Things I'd like whatis to have:
Date:	Wed, 10 Mar 1993 17:16:16 -0500
Message-Id: <9303101716.aa10551@ceres.srg.af.mil>

To me this seems like an idea worth at least considering, it would also
be nice to have an option to see the whole chain of candidates.  (the
function and possibly the builtin or executable(s))  I once had a
function, that called a script, that called the binary, all with the
same name, and it stopped working when another version appeared in my
path.  (Memory falters on whether this was from changing the $path or
an executable in a new place.)

I ended up writing the following rc function to tell me where an
executable was (or could be) coming from.  It should probably also
check if there is a function by the name given, before listing the
executable files, but I tend to know what functions are in my .rcrc
file.

fn whereis { i=() p=() { 
	for (i)
		for (p in $path)
			if (test -f $p/$i -a -x $p/$i)
				echo $p/$i
}}