|
- What is the difference between . . and source? [duplicate]
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
- 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
- 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 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
- networking - Ephemeral port : What is it and what does it do? - Unix . . .
I suddenly came across the term "ephemeral port" in a Linux article that I was reading, but the author did not mention what it is What is an ephemeral port in UNIX?
- 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
- How to determine where an environment variable came from?
You'll need to complete a few actions and gain 15 reputation points before being able to upvote Upvoting indicates when questions and answers are useful What's reputation and how do I get it? Instead, you can save this post to reference later
- Why doesnt my Bash script recognize aliases?
In my ~ bashrc file reside two definitions: commandA, which is an alias to a longer path commandB, which is an alias to a Bash script I want to process the same file with these two commands, so I
|
|
|