🚀 go-pugleaf

Has anybody seen the following behavior in ksh?

Assuming that the current directory is /usr/me (this does not affect the bug)

1. make a subdirectory of the current directory that contains a colon in it:
    "mkdir c:"

2. cd to that directory: "cd c:" Current directory is now /usr/me/c:

3. make a subdirectory of the current directory: "mkdir xyz"

4. cd to that directory: "cd xyz"

you should get: "ksh: xyz not found"

However, if you type cd ../c:/xyz you will have your current directory set to
/usr/me/c:/xyz with no complaints. (".." appears to mean TWO directories up
in this case!)

Now with your current directory set to /usr/me/c:/xyz type "cd ..".
Your new current directory is /usr/me! It moved you up TWO directories!

This was done on a VAX8600 running AT&T SYSTEMV Release 2.2 with the
11/16/88 ksh. ksh was the login shell and CDPATH was null.

Is this a bug? Or am I missing something in the way ksh deals with CDPATH?

This doesn't happen on our older ksh which was the version of 2/21/85.

-------------------------------------------------------------------------------
 #include <standard/disclaimer.h>  |  LIFE IS NOT A MALFUNCTION! - Number 5 
    ____  ___ _  _  __ ____     ____    _ _  ___  ___   _ _   ____
    /  / /  /  | /  /  /  /      /     //// /  / /  /   / /  /___
   /  / /--/   |/  /  /  /   /  /     /  / /--/ /--\   / \      /
  ~~~~ ~  ~    ~  ~~ ~~~~    ~~~  ~  ~  ~ ~  ~ ~   ~  ~  ~  ~~~~
Pony Express:                      |    Electric Avenue:
=============                      |    ================
David J. Marks                     |    ...!mcnc!rti!tijc02!djm408
M/S 3520                           |
Texas Instruments                  |    Ma Bell:
Erwin Highway/P. O. Drawer 1255    |    ========
Johnson City, TN. 37605            |    615-461-2074