|
- What is the difference between . . and source?
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
- Source shell script automatically in terminal
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 I need
- How to export variables from a file? - Unix Linux Stack Exchange
A dangerous one-liner that doesn't require source: export $(xargs <file) It can't handle comments, frequently used in environment files It can't handle values with whitespace, like in the question example It may unintentionally expand glob patterns into files if they match by any chance It's a bit dangerous because it passes the lines through bash expansion, but it has been useful to me when I
- How can I source expect script - Unix Linux Stack Exchange
The fundamental problem is that a child process cannot alter the environment of its parent This is why you need to source that shell script, so the environment variables will persist in your current shell Expect is designed to spawn child processes Your current shell cannot be affected by the result of expect test exp However, you can spawn a shell, source that shell script, and then keep
- 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, 5 months ago Modified 4 years, 10 months ago
- Why does source give an error cannot execute binary file
The source command will: Read and execute commands from the filename argument in the current shell context If filename does not contain a slash, the PATH variable is used to find filename This behaviour is defined (for , its alias) by POSIX Why? Well, you can put sourceable configuration scripts inside PATH and access them without a qualified path To access the file you want, give an
|
|
|