Xref: utzoo comp.bugs.sys5:1040 comp.unix.questions:15065
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!dptg!ulysses!andante!alice!debra
From: debra@alice.UUCP (Paul De Bra)
Newsgroups: comp.bugs.sys5,comp.unix.questions
Subject: Re: Is this a ksh bug?
Message-ID: <9648@alice.UUCP>
Date: 20 Jul 89 14:45:19 GMT
References: <554@tijc02.UUCP>
Reply-To: debra@alice.UUCP ()
Organization: AT&T, Bell Labs
Lines: 30

In article <554@tijc02.UUCP> djm408@tijc02.UUCP (David Marks         ) writes:
}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"
}...
Yep, happens here too.
Don't know what causes it. I can make a guess of course.
It looks like names starting with 'something:' are interpreted as
meaning go to machine 'something'... (just a guess).

My machine is a Microvax II running the ninth edition Unix.
The ksh was taken from "alice" and is dated February 29, 1989.

Paul.

-- 
------------------------------------------------------
|debra@research.att.com   | uunet!research!debra     |
------------------------------------------------------