Message186666
Uh, confusion. Indeed, "PATH= foo" finds foo in the current directory on bash. I'm not sure how I ran the original example. It seems that a default PATH is used, which includes at least "/bin" and ".".
The point I was making in the original post is still valid: "PATH= foo" appears to behave identically to "unset PATH && foo" in all cases I tried so far. For example, for me both work with some local executable or with "ls" (which is in /bin), and neither works with "which" (which is in /usr/bin). |
|
Date |
User |
Action |
Args |
2013-04-12 18:55:27 | arigo | set | recipients:
+ arigo, pitrou, Arfrever, r.david.murray, cvrebert, asvetlov, python-dev, eric.snow, serhiy.storchaka, kachayev, tvaughan |
2013-04-12 18:55:27 | arigo | set | messageid: <1365792927.22.0.165386581644.issue16309@psf.upfronthosting.co.za> |
2013-04-12 18:55:27 | arigo | link | issue16309 messages |
2013-04-12 18:55:26 | arigo | create | |
|