<JacobWeisz[m]>
So if you have an executable in the current directory and PATH with the same name on a Linux system, which does it prefer or is that setting specific?
<isd>
ocdtrekkie: by default it doesn't search the current directory at all and you have to explicitly do ./foo or whatever (if there's a slash in the name it treats it as a path directly rather than searching PATH)
<isd>
You can put "." in $PATH somewhere to get it to search the current directory
<JacobWeisz[m]>
Okay, I want to clean up that version crud in the release script for vagrant-spk, and I figure being explicit is key, since I may have a release copy in my path, and the version I am working on releasing in my working directory.
<isd>
Yeah, I generally advise against having "." in 4PATH
<isd>
*$PATH
<TimMc>
Yes, not something you generally want to do. :-)
<TimMc>
For security reasons, but also for predictability.