Source Code Meditation Source Code Meditation

Source Code Meditation Source Code Meditation 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 environment changes are kept. source script this also sources the script. the source command is not required by posix and therefore is less portable than the shorter. 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 command line.

Source Code Meditation Source Code Meditation 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 same reason. 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 defined in man bash as an array of source filenames corresponding to shell functions?. 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 bang line would suggest you are). source is not posix. using source on dash does not work, only . works. 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 is to start fr.

Source Code Meditation Source Code Meditation 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 bang line would suggest you are). source is not posix. using source on dash does not work, only . works. 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 is to start fr. In my ~ .bashrc file reside two definitions: commanda, which is an alias to a longer path commandb, which is an alias to a bash script i want to process the same file with these two commands, so i. I.e., unpack the source package from your distribution, replace the source with the upstream version, check if any of the distribution's patches or configuration tweaks still apply, build the binary package (make sure you changed the version of the packaged stuff!) and install that one. yes, it is more work than just building and installing. The original sh sourced .profile on startup. bash will try to source .bash profile first, but if that doesn't exist, it will source .profile 1. note that if bash is started as sh (e.g. bin sh is a link to bin bash) or is started with the posix flag, it tries to emulate sh, and only reads .profile. footnotes: actually, the first one of .bash profile, .bash login, .profile see also: bash. What is the difference between sourcing ('.' or 'source') and executing a file in bash? ask question asked 13 years ago modified 4 years, 5 months ago.