What is the source command used for?

The source command is used to execute shell scripts in the current shell context, allowing variables and functions defined in the script to be available in the current shell session.

How is source different from executing a script directly?

When you use 'source script.sh', the script runs in the current shell context, while executing 'script.sh' directly creates a new subshell. This means variables and functions from sourced scripts persist in your current session.

What is the dot (.) equivalent of source?

The dot (.) command is equivalent to source - both 'source script.sh' and '. script.sh' do the same thing. The dot notation is more portable across different shells.

source

Execute shell scripts in the current shell context

Syntax

source filename [arguments]

. filename [arguments]

Basic Usage

Source a configuration file

source ~/.bashrc

Executes the bashrc file in the current shell context.

Source using dot notation

. ~/.bashrc

Same as source, but more portable across shells.

Source with arguments

source config.sh production

Source from current directory

source ./local_config.sh

Key Differences

source vs Direct Execution

source script.sh: Runs in current shell context
./script.sh: Creates new subshell
Variables: Sourced scripts can modify current shell variables
Functions: Functions defined in sourced scripts are available in current shell
Environment: Changes persist after script execution

Practical Examples

Reload shell configuration

source ~/.bashrc

Load environment variables

source .env

Load custom functions

source ~/scripts/functions.sh

Load project configuration

source project_config.sh

Load with conditional logic

                        if [ -f ~/.local_config ]; then

                          source ~/.local_config

                        fi

Source multiple files

                        source ~/.aliases

                        source ~/.functions

                        source ~/.exports

Load development environment

source venv/bin/activate

Common Use Cases

When to Use source

Configuration Files: Loading shell configuration files
Environment Setup: Setting environment variables
Function Libraries: Loading custom functions
Development Tools: Activating virtual environments
Project Setup: Loading project-specific configurations
Alias Definitions: Loading custom aliases

Shell Compatibility

Shell Support

bash: Supports both 'source' and '.'
zsh: Supports both 'source' and '.'
ksh: Supports both 'source' and '.'
sh: May only support '.' (POSIX compliant)
csh/tcsh: Uses 'source' command

Best Practices

When to Use

Loading configuration files
Setting up development environments
Loading function libraries
Reloading shell configurations
Project-specific environment setup

Important Notes

Use '.' for better POSIX compatibility
Sourced scripts can modify your current shell environment
Be careful when sourcing untrusted scripts
Variables and functions persist after sourcing
Use 'source' for bash-specific scripts
Consider using '.' for portable scripts
Always verify the content of scripts before sourcing