PATH bug?

[Guy Harris]

> > If the current directory is specified as the last directory searched using
> > a trailing ":" instead of ":." (in $PATH) then sh will not find executable
> > files in the current directory.
> 
> Try two trailing colons.  If you read the (post-V7) manual page very
> carefully, this behavior is documented:  colon is effectively functioning
> as a terminator rather than as a separator.

For those without a) post-V7 documentation for the Bourne shell or b) the
patience to try to find it, the magic sentence is:

	Execution
	     ...Note that the current directory is specified by a
	     null path name, which can appear immediately after the
	     equal sign or *between the colon delimiters* anywhere
	     else in the path list.

The italicized phrase is the obscure clue.

	Guy Harris