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 …

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 …

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 …

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 …

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, 8 months ago

My comment is just a stronger statement of Ilmari Karonen's 2014 comment. It is factually incorrect to say ".bashrc runs on every interactive shell launch". A login shell is an interactive …

It’s a scope problem. As designed, the _source_script function is, effectively, calling itself recursively, inasmuch as it is doing . ./${!arg}.sh and sourcing files that call _source_script. But …

Is it possible to compare two directories with rsync and only print the differences? There's a dry-run option, but when I increase verbosity to a certain level, every file compared is shown. ls -a...

Being on Linux, your shell is Bash, so you need to source the settings64.sh file. You do that by typing in the command just as you yourself has typed it in the question:

Source .bashrc file in bash globally Ask Question Asked 8 years, 9 months ago Modified 5 years, 7 months ago