|
- What is the difference between . . and source? [duplicate]
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 vs . why different behaviour? - Unix Linux Stack Exchange
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
- What is the difference between . and source in shells?
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
- kernel martian source to and from same IP - Unix Linux Stack Exchange
We are intermittently seeing kernel: martian source log entries for eth0 on a couple of our servers The interesting thing is that they are to and from the same IP For instance: Nov 4 02:20:27
- bash - Revert . or source - Unix Linux Stack Exchange
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
- shell - What is the difference between sourcing (. or source) and . . .
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
- scp copy direction: what is source, what is target?
And most allow multiple sources before the final target if it makes sense to do so That includes scp Some commands (like the GNU versions of cp and mv) have an option (e g -t or --target-directory=DIRECTORY) that allow you to put the target first - but the default is the standard "source (s) before target"
- If bash lt;file gt; works, why is source lt;file gt; throwing an error?
However, when you source something, it is run in your current shell which, because it is interactive, has already loaded the aliases and therefore the fi alias is recognized and breaks the sourcing
|
|
|