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
bash - Revert . or source - Unix Linux Stack Exchange I accidentally sourced the wrong environment from a script Is there any way to 'unsource' it or in other words to revert it and restore the previous environment? The obvious answer is to start fr
How can I source environment changes system-wide? Similarly, source ing etc profile after a change will make those changes effective in your current session But suppose you need to change an environment variable that is defined in etc profile (or somewhere under etc profile d ) and want the change to be visible across all sessions of all users on the system immediately
linux - `source` command: . csh and . sh file not found even though `ls . . . The shell is complaining about the source command, not about your files Your shell seems to be bin sh, which may be the dash shell When dash is running as sh, it's a POSIX shell and therefore does not have a source command The source command is an extension to the standard, usually the same or similar as the standard (dot) command Therefore, if you want to source those files in your