From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from relay2.UU.NET ([137.39.1.7]) by hawkwind.utcs.toronto.edu with SMTP id <2743>; Thu, 25 Jun 1992 18:11:36 -0400
Received: from uunet.uu.net (via LOCALHOST.UU.NET) by relay2.UU.NET with SMTP 
	(5.61/UUNET-internet-primary) id AA03797; Thu, 25 Jun 92 18:11:30 -0400
Received: from srg.UUCP by uunet.uu.net with UUCP/RMAIL
	(queueing-rmail) id 181006.19271; Thu, 25 Jun 1992 18:10:06 EDT
Received: from ceres.srg.af.mil by srg.srg.af.mil
	id aa09729; Thu, 25 Jun 92 17:56:31 EDT
From:	culliton@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: Command execution
Date:	Thu, 25 Jun 1992 17:56:35 -0400
Message-Id: <9206251756.aa10707@ceres.srg.af.mil>

cks> 						if you invoke the absolute
cks> path name, you *mean* the absolute path name.

I can still imagine ways that it might be useful, but no big deal.

cks>  'x/y' vs. './x/y' has been hashed out before in the mailing list;
cks> check the archives. I belive Pike just considered it the right
cks> approach. I use it for the same sort of things that David Moore does;
cks> to keep infrequently-used stuff off my path.

I probably missed it, having only been on the mailing list since early
December.  It could definitely be made clearer in the man page,
especially since it's rather different from most shells.