Xref: utzoo comp.bugs.sys5:1061 comp.unix.questions:15243
Path: utzoo!utgpu!watmath!att!cbnewsc!dwd
From: dwd@cbnewsc.ATT.COM (david.w.dykstra)
Newsgroups: comp.bugs.sys5,comp.unix.questions
Subject: Re: Is this a ksh bug?
Message-ID: <2089@cbnewsc.ATT.COM>
Date: 27 Jul 89 21:50:44 GMT
References: <1260@cbnewsl.ATT.COM>
Organization: AT&T Bell Laboratories
Lines: 31

From article <1260@cbnewsl.ATT.COM>, by raj@cbnewsl.ATT.COM (Richard A. Johnson):
 > In article <1925@cbnewsc.ATT.COM>, levy@cbnewsc.ATT.COM (Daniel R. Levy) writes:
 >> 
 >> I was one of the beta testers for the '88 ksh, and to the best of my memory,
 >> this bug is in the 11/16/88 ksh, but not in the 11/16/88a ksh or earlier '86
 >> ksh.
 >> 
Yes, here's the line from RELEASEa:
	q.  If the name of the directory you are in contained a :,
	    a cd command to a relative pathname did always work correctly.
						   ^
					I assume 'not' goes here.

 > I was also a beta-tester and am now running ksh version 11/16/88a.
 > The bug does appear on my 3B2 running SVR3.1, and can be reproduced
 > as follows (in case there is still a question about what the bug is):
 > 
 > 	$ CDPATH=/usr:/usr/raj
 > 	$ export CDPATH
 > 	$ cd /usr/raj
 > 	$ mkdir c:
 > 	$ cd c:
 > 	$ mkdir xyz
 > 	$ cd xyz
 > 	ksh: xyz:  not found
 > 	$
That's not a bug, that's a feature!  Your CDPATH does not include '.' so
cd will not search your current directory.

- Dave Dykstra
  ttrdf!dwd