Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • Apologies if this is a duplicate - upon further investigation, I found some pages with relevant information by searching for 'bash dot' instead of 'bash .'. Commented Jul 25, 2012 at 6:32
  • 6
    Just as test.sh is not the same as ./test.sh (the first invokes a PATH search), so are . test.sh and . ./test.sh different in the same way (the former invokes a PATH search). Many shells seem to implicitly include . at the end of PATH when doing a . path search, but this behavior is not standard. Thus, it is more accurate to compare test.sh vs . test.sh and ./test.sh vs . ./test.sh. Commented Jul 30, 2012 at 21:13