|
- 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
- What is the difference between ~ . profile and ~ . bash_profile?
The original sh sourced profile on startup bash will try to source bash_profile first, but if that doesn't exist, it will source profile Note that if bash is started as sh (e g bin sh is a link to bin bash) or is started with the --posix flag, it tries to emulate sh, and only reads profile Footnotes: Actually, the first one of bash_profile, bash_login, profile See also: Bash
- bash script error: source: not found - Unix Linux Stack Exchange
Using source on dash does not work, only works My test with source with bash in POSIX mode worked, though maybe this is due to my version or compilation flags
- What does :source % mean? - Unix Linux Stack Exchange
When I added a vim plugin, VimAwesome document said that :source % What does this mean? I'd like to understand % meaning
- What is the purpose of . bashrc and how does it work?
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 shell, and it's the counterexample: a login shell does not run bashrc It would be correct to say " bashrc is run by every interactive non-login shell" Bash Reference Manual, section 6 2, "Bash Startup FIles"
- Use config file for my shell script - Unix Linux Stack Exchange
36 source is not secure as it will execute arbitrary code This may not be a concern for you, but if file permissions are incorrect, it may be possible for an attacker with filesystem access to execute code as a privileged user by injecting code into a config file loaded by an otherwise-secured script such as an init script
- 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 12 years, 11 months ago Modified 4 years, 3 months ago
|
|
|