|
- Source vs . why different behaviour? - Unix Linux Stack Exchange
source is a shell keyword that is supposed to be used like this: sourcefile 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?
source is there for readability and self-documentation, exists because it is quick to type The commands are identical The commands are identical Perl has long and short versions of many of its control variables for the same reason
- What does :source % mean? - Unix Linux Stack Exchange
The :source % command, when used on the ~ vimrc configuration, will reload the config You can achieve the same effect by quitting and restarting Vim, but this is faster Note that your Vim configuration needs to be cleanly written for that to work
- What is the difference between ~ . profile and ~ . bash_profile?
bash will try to source bash_profile first, but if that doesn't exist, it will source profile 1 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:
- Cant use `source` from cron? - Unix Linux Stack Exchange
Unless you have written a script called source and put it in , you want source and not source The next issue is that cron usually uses whatever you have as bin sh and source is a bashism (or other such more complex shells) The portable, POSIX-compliant command for sourcing a file is So, try that instead of source:
- shell - What is the difference between sourcing (. or source) and . . .
$ file # that exact same file as above, now it is sourced $ source file # an equivalent (but longer) command Of course, if the directory is not set in the path (not starting dot), some searching will be involved to find the specific file to be sourced In bash:
- How to export variables from a file? - Unix Linux Stack Exchange
is the standard and Bourne name for the source command so I prefer it for portability (source comes from csh and is now available in most modern Bourne-like shells including bash though (sometimes with a slightly different behaviour)) In POSIX shells, you can also use set -o allexport tmp txt set +o allexport
|
|
|