Sep 27, 2016 · When the script is done, any changes that it made to the environment are discarded. . script The above sources the script. It is as if the commands had been typed in directly. Any …

source is a shell keyword that is supposed to be used like this: source file where file contains valid shell commands. These shell commands will be executed in the current shell as if typed from the …

2 source is there for readability and self-documentation, . exists because it is quick to type. The commands are identical. Perl has long and short versions of many of its control variables for the …

You have an alias which is overriding the builtin source (fix with unalias source) You have a function which is overriding source (fix with unset -f source) You are somehow not using bash (although your …

Jul 30, 2020 · I've read that BASH_SOURCE should be populated with the name of the executing script (and it works!). But why does BASH_SOURCE hold the name of the executing script, when it is …

It looks like BASH_SOURCE is actually an array, so it's better to use its last element, via "${BASH_SOURCE[-1]}", as @gkb0986 explains here and as I show in my brand new answer here, …

I used to think that the built-ins . and source are equivalent. This question agrees with me when it comes to bash. However I encountered the following using zsh: desktop ~/pst . env /usr/bin/e...

What is the difference between sourcing ('.' or 'source') and executing a file in bash? Ask Question Asked 13 years, 4 months ago Modified 4 years, 9 months ago

Mar 17, 2018 · I accidentally sourced the wrong environment from a script. Is there any way to 'unsource' it or in other words to revert it and restore the previous environment? The obvious answer …

Apr 4, 2015 · How can I automatically source a particular shell script when I open a terminal window by right clicking somewhere and choosing "open in terminal"? For example, every time I open a terminal …