If file does not contain a <slash>, the shell shall use the search path specified by PATH to find the directory containing file. Unlike normal command search, however, the file searched for by the dot utility need not be executable. If no readable file is found, a non-interactive shell shall abort; an interactive shell shall write a diagnostic message to standard error, but this condition shall not be considered a syntax error. (SUSv7 but unchanged I think.)
@ripienaar@b0rk I think bash has always had `source`, which is a csh-ism that was never in the Bourne or Korn shell, and it's always been equivalent to the `.` command going back to pre-1.x days.
I am learning some upsetting-to-me things from reading the bash man page, for example that in bash `source blah.sh` will by default search all directories in your PATH for a file called `blah.sh`
@malte@wesmorgan1@b0rk@Xavier Yeah same there, in fact I'd more except some kind of BASH_PATH if it really wanted to resolve something, quite like there is an LD_LIBRARY_PATH.
@wesmorgan1@b0rk@Xavier but "source" is for sourcing bash-script, which could even be 600 permissionwise, while $PATH contains _executables_ of all sort of flavours?