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 …

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 …

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 …

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 …

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, …

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 …

Oct 14, 2017 · When I try to use source from the cron job (I have tried both directly in crontab and in a script called by crontab) it doesn't seem to work. I made a simplified version of my project …

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

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...

Sep 28, 2024 · Although the contents (size) in bytes of both source and destination are the same, the amount of space it takes up is less on the local HDD compared to the amount it takes up …