RE: [**EXTERNAL**] Re: [PATCH] ash: make bash_source command search current directory after PATH

>I fought through the bash startup scripts almost 20 years ago in >college, and still have "source .bashrc" in my ~/.bash_profile that >I've >been carrying from system to system ever since :-) >and my PATH has never had '.' in it.  Your explanation makes >perfect sense though. My understanding

Re: [**EXTERNAL**] Re: [PATCH] ash: make bash_source command search current directory after PATH

On Fri, Jan 26, 2018 at 10:47 AM, Cathey, Jim wrote: > My understanding, from years past, is that "source " (or ". ") > is _exactly_ the same as "", except that it's running in _this_ shell > rather than in a subshell. Thus it is able to affect environment variables > that

RE: [**EXTERNAL**] Re: [PATCH] ash: make bash_source command search current directory after PATH

My understanding, from years past, is that "source " (or ". ") is _exactly_ the same as "", except that it's running in _this_ shell rather than in a subshell. Thus it is able to affect environment variables that subsequent commands can inherit, etc. If "." is not in your PATH, and you want