copy and paste this google map to your website or blog!
Press copy button and paste into your blog or website.
(Please switch to 'HTML' mode when posting into your blog. Examples: WordPress Example, Blogger Example)
Input Form:Deal with this potential dealer,buyer,seller,supplier,manufacturer,exporter,importer
(Any information to deal,buy, sell, quote for products or service)
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
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
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"
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
How can I make a script in etc init. d start at boot? I think I read something a while back about this, but I can't remember how it's done Essentially, I have a service in etc init d which I'd like to start automatically at boot time I remember i