🚀 go-pugleaf

In article <phil.659145660@adam.adelaide.edu.au> phil@adam.adelaide.edu.au (Phil Kernick) writes:
>
> I have found what I also believe to be a bug in SKsh.
> 
> I have my path set to
> 
> ".,lc:,uucp:c"
> 
> with the command compress in uucp:c and the command touch in lc:
> 
> now I go into a directory with an executable called compress and
> an executable called touch.
> 
> if I type compress it uses my compress in the current directory.
> if I type touch it uses touch in the lc: directory.
> 
> Both are executable, and which tells me it should execute the
> command from the current directory.
> 
> if I use ./touch it works.  any ideas?

This sounds precisely like what will happen if you made lc:touch resident
at some point.  The resident list used by SKsh gets searched before the
path spec.  Use "resident" to see if it's on the list.

This is assuming you have disabled the builtin "touch" command (with an
"unset -b touch" cmd, or used something like "alias touch $(which touch)",
etc), and really are executing the lc:touch when you think you are (and
not the builtin).  What do "whence touch" and "which touch" tell you?

/kim

-- 
UUCP:  kim@uts.amdahl.com   -OR-   ked01@juts.ccc.amdahl.com
  or:  {sun,decwrl,hplabs,pyramid,uunet,oliveb,ames}!amdahl!kim
DDD:   408-746-8462
USPS:  Amdahl Corp.  M/S 249,  1250 E. Arques Av,  Sunnyvale, CA 94086
BIX:   kdevaughn     GEnie:   K.DEVAUGHN     CIS:   76535,25