I use my own preferred functions for 'dirs' etc., and am having difficulty
getting them recognized without explicitly sourcing them.
For the purpose of this example, I have a version with easily recognizable
behaviour:
Script started on Tue 03 Aug 2010 02:29:56 PM EDT
$ cat /tmp/test/fun/dirs
function dirs
{
print -- 'My dirs!'
}
I added a corresponding bin/.paths for good measure:
$ cat /tmp/test/bin/.paths
FPATH=../fun
I start a new, clean ksh, with PATH and FPATH explicitly set so that mine comes
first (here /opt/att is a symlink to, in this case,
/opt/ast/arch/linux.i386-64):
$ env - \
> PATH=/tmp/test/fun:/tmp/test/bin:/bin:/usr/bin:/opt/att/bin \
> FPATH=/tmp/test/fun \
> ksh
Now:
$ type dirs
dirs is an undefined function
$ dirs
1) ~/home/kpschoed
Not my function, obviously. I don't understand why.
"Insanity is doing the same thing over and over again but expecting different
results", so here goes:
$ unset -f dirs
$ type dirs
dirs is an undefined function
$ dirs
My dirs!
Could someone clue me in on what's happening here?
--
Kevin Schoedel <[email protected]> VA3TCS
_______________________________________________
ast-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/ast-users
