>I was unable to reproduce this. There is only one reason that I can think of
>that would execute a different dirs. If dirs was defined in the /etc/ksh.kshrc
>file. However, in this case
> type dirs
>would not give dirs is an undefined function.
>Maybe running under strace (or truss) will give a clue.
That was not the problem, but strace did help me understand the function search
a little better; I should have done it earlier.
> print ${.sh.version}
Tried Version JM 93t+ 2010-03-05 and Version JM 93t+ 2010-06-21.
>Did you make the dirs function executable? Does this fix the problem?
Indeed it does. I still don't understand what was going on -- why the behaviour
was different after the unset, and different between platforms -- but
pragmatically I think it solves my problem: I just need to switch to using
.paths exclusively.
Thanks,
--
Kevin Schoedel <[email protected]> VA3TCS
_______________________________________________
ast-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/ast-users