thanks for the report it took some experimentation to reproduce it occurs when . is on PATH
$ PATH=:/bin /bin/ksh -c 'whence -a true' true is a shell builtin true is a tracked alias for /tmp/true $ PATH=/bin: /bin/ksh -c 'whence -a true' true is a shell builtin true is a tracked alias for /bin/true $ PATH=/foo /bin/ksh -c 'whence -a true' true is a shell builtin no fix or workaround yet On Thu, 15 Nov 2007 11:20:28 -0500 (EST) [EMAIL PROTECTED] (Dave Morano) wrote: > In both the latest release of KSH (and I think the previous one) > the behavior of 'whence' seems strange. > $ > $ pwd > /home/me/a > $ # do a 'whence -a' on a regular program > $ whence -a proga > proga is a tracked alias for /usr/local/bin/proga > $ > $ # now do a 'whence -a' on a SHELL builtin > $ ls cut > ls: cut: No such file or directory > $ whence -a cut > cut is a shell builtin > cut is a tracked alias for /home/me/a/cut > $ > $ > Why does 'whence -a' always show builtins as being a "tracked alias" > for something in the current working directory that doesn't even exist? > Is this the proper behavior? This seems a bit strange to me. > Thanks for any information, > Dave Morano > [EMAIL PROTECTED] _______________________________________________ ast-developers mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-developers
