Pio2pio at 23:35, 8 October 2018

2018-10-08T23:35:04Z

← Older revision		Revision as of 01:35, 9 October 2018
Line 4:		Line 4:

	You can source any runnable shell script. The end effect will be the same as if you had typed the commands in the script into your terminal. For example, if the script changes directories, when it finishes running, your current working directory will have changed.		You can source any runnable shell script. The end effect will be the same as if you had typed the commands in the script into your terminal. For example, if the script changes directories, when it finishes running, your current working directory will have changed.
			<source lang="bash">
			source my-script.sh;
			. my-script.sh;
			</source>
			Both commands will have the same effect. In contrast, passing the script filename to the desired shell will run the script in a subshell, not the current context.

			= Excuting versus sourcing a script =
			When you <tt>execute</tt> a shell script, the script runs in a new shell. Any changes to the environment caused by the script are scoped to the new shell.
			<source lang="bash">
			./my-script.sh
			</source>

	~~source my-script.sh;~~
	~~. my-script.sh;~~

	~~Both commands will have the same effect. In contrast~~, ~~passing~~ the script ~~filename~~ to the ~~desired shell will run~~ the script ~~in a subshell, not~~ the current ~~context~~.		When you source a shell script, the script runs in the current shell. Any changes to the environment caused by the script will affect the current shell.
			<source lang="bash">
			source my-script.sh
			</source>

Pio2pio: Created page with "This is often used to import environment variables to current session. Running the command `source` on a script executes the script within the context of the curre..."

2016-02-26T13:22:40Z

Created page with "This is often used to import environment variables to current session. Running the command <code>source</code> on a script executes the script within the context of the curre..."

New page

This is often used to import environment variables to current session.

Running the command <code>source</code> on a script executes the script within the context of the current process. This means that environment variables set by the script remain available after it's finished running. This is in contrast to running a script normally, in which case environment variables set within the newly-spawned process will be lost once the script exits.

You can source any runnable shell script. The end effect will be the same as if you had typed the commands in the script into your terminal. For example, if the script changes directories, when it finishes running, your current working directory will have changed.

source my-script.sh;
. my-script.sh;

Both commands will have the same effect. In contrast, passing the script filename to the desired shell will run the script in a subshell, not the current context.

Linux - source a script - Revision history

Pio2pio at 23:35, 8 October 2018

Pio2pio: Created page with "This is often used to import environment variables to current session. Running the command source on a script executes the script within the context of the curre..."

Pio2pio: Created page with "This is often used to import environment variables to current session. Running the command `source` on a script executes the script within the context of the curre..."