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
Unable to detect Python kernels in VS Code Jupyter notebooks after . . . Based on your solving attempt log the reason can be in version of VS code Jupyter extension that periodically breaks this feature E g for me 2025 5 2025051601 kernels are shown and 2025 7 2025072101 gives empty list The solution is to "install specific version" under uninstall drop down menu to try some more stable not the latest version
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
How to export variables from a file? - Unix Linux Stack Exchange A dangerous one-liner that doesn't require source: export $(xargs <file) It can't handle comments, frequently used in environment files It can't handle values with whitespace, like in the question example It may unintentionally expand glob patterns into files if they match by any chance It's a bit dangerous because it passes the lines through bash expansion, but it has been useful to me when I
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