> > I'm getting strange behaviour from ksh which perhaps someone could
> > explain to me.
> Yes, that is serious brain damage!
> > %cd /tmp
> > %mkdir a:b
> > %cd a:b
> > %mkdir z
> > %cd z
> > at that point ksh tells me:
> > ksh: z: not found
> Try the following:
> cd a:b/z
> cd ..
> puts you back in /tmp
> But what gives an indication of what is happening
> do in /tmp also:
> mkdir a a/z
> cd a:b
> cd z
> and now you are in /tmp/a/z, not /tmp/a:b/z.
> I just checked the source (11/16/88). The reason is that ksh (before doing
> the cd) constructs the absolute path of the directory where you are going to
> cd to. For this it uses a routine that is also used when building the
> absolute pathname getting a choice of paths you give when setting CDPATH.
> And guess what? Yes, pathnames in CDPATH are colon separated. Ksh ought
> to distinguish more between cd'ing through CDPATH or directly.
I emailed Korn on this some time ago, and got a reply that he was aware
of this problem, and this is/was being fixed. We later grabbed a newer copy
of ksh (we currently have 11/16/88f), in which it was/is fixed. Check to
see what rev you have, and get something newer (I think that 111688b was one
where we saw the problem, but maybe not).
Hope this helps.
\ Calvin Hayden Uucp: ...!uunet!tijc02!cgh018 \
~~~~~~~~~~~~ My personal opinions and mine alone! ~~~~~~~~~~~~~~~~~~