<?xml version="1.0" encoding="utf-8" ?><rss version="2.0"><channel><title>Bing: Source Code GIF Animation</title><link>http://www.bing.com:80/search?q=Source+Code+GIF+Animation</link><description>Search results</description><image><url>http://www.bing.com:80/s/a/rsslogo.gif</url><title>Source Code GIF Animation</title><link>http://www.bing.com:80/search?q=Source+Code+GIF+Animation</link></image><copyright>Copyright © 2026 Microsoft. All rights reserved. These XML results may not be used, reproduced or transmitted in any manner or for any purpose other than rendering Bing results within an RSS aggregator for your personal, non-commercial use. Any other use of these results requires express written permission from Microsoft Corporation. By accessing this web page or using these results in any manner whatsoever, you agree to be bound by the foregoing restrictions.</copyright><item><title>What is the difference between "." "./" and "source"?</title><link>https://unix.stackexchange.com/questions/312573/what-is-the-difference-between-and-source</link><description>The above executes the script. 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 ..</description><pubDate>Sat, 25 Apr 2026 21:53:00 GMT</pubDate></item><item><title>Source vs . why different behaviour? - Unix &amp; Linux Stack Exchange</title><link>https://unix.stackexchange.com/questions/309768/source-vs-why-different-behaviour</link><description>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.</description><pubDate>Sat, 25 Apr 2026 23:48:00 GMT</pubDate></item><item><title>What is the difference between '.' and 'source' in shells?</title><link>https://unix.stackexchange.com/questions/58514/what-is-the-difference-between-and-source-in-shells</link><description>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.</description><pubDate>Sat, 25 Apr 2026 11:38:00 GMT</pubDate></item><item><title>bash script error: source: not found - Unix &amp; Linux Stack Exchange</title><link>https://unix.stackexchange.com/questions/116584/bash-script-error-source-not-found</link><description>You have an alias which is overriding the builtin source (fix with unalias source) You have a function which is overriding source (fix with unset -f source) You are somehow not using bash (although your bang line would suggest you are). source is not POSIX. Using source on dash does not work, only . works.</description><pubDate>Fri, 24 Apr 2026 04:22:00 GMT</pubDate></item><item><title>What is the difference between building from source and using an ...</title><link>https://unix.stackexchange.com/questions/152346/what-is-the-difference-between-building-from-source-and-using-an-install-package</link><description>I.e., unpack the source package from your distribution, replace the source with the upstream version, check if any of the distribution's patches or configuration tweaks still apply, build the binary package (make sure you changed the version of the packaged stuff!) and install that one. Yes, it is more work than just building and installing.</description><pubDate>Thu, 23 Apr 2026 17:24:00 GMT</pubDate></item><item><title>shell - What is the difference between sourcing ('.' or 'source') and ...</title><link>https://unix.stackexchange.com/questions/43882/what-is-the-difference-between-sourcing-or-source-and-executing-a-file-i</link><description>What is the difference between sourcing ('.' or 'source') and executing a file in bash? Ask Question Asked 13 years, 9 months ago Modified 5 years, 1 month ago</description><pubDate>Sat, 25 Apr 2026 06:51:00 GMT</pubDate></item><item><title>Where to download Linux Kernel source code of a specific version ...</title><link>https://unix.stackexchange.com/questions/46077/where-to-download-linux-kernel-source-code-of-a-specific-version</link><description>Is there a resource to download a specific kernel version source? For example, I want to get 2.6.36.2 sources to compare with this package and see what changes were introduced?</description><pubDate>Sat, 25 Apr 2026 17:57:00 GMT</pubDate></item><item><title>How to download a Debian package's source code?</title><link>https://unix.stackexchange.com/questions/121041/how-to-download-a-debian-packages-source-code</link><description>A second possibility is to download the source code from upstream directly instead of downloading it from Debian repositories. This has the advantage that if you not only want to read the source code but might like to change something you can directly commit and submit it to upstream (assuming it is not a Debian patch).</description><pubDate>Thu, 16 Apr 2026 20:24:00 GMT</pubDate></item><item><title>What is the difference between ~/.profile and ~/.bash_profile?</title><link>https://unix.stackexchange.com/questions/45684/what-is-the-difference-between-profile-and-bash-profile</link><description>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 ...</description><pubDate>Fri, 24 Apr 2026 03:18:00 GMT</pubDate></item><item><title>" sudo: source: command not found" - Unix &amp; Linux Stack Exchange</title><link>https://unix.stackexchange.com/questions/202332/sudo-source-command-not-found</link><description>34 source is a shell builtin, so it cannot be executed without the shell. However, by default, sudo do not run shell. From sudo Process model When sudo runs a command, it calls fork (2), sets up the execution environment as described above, and calls the execve system call in the child process If you want to explicitly execute shell, use -s option:</description><pubDate>Sat, 25 Apr 2026 04:50:00 GMT</pubDate></item></channel></rss>