Source code in c. 2 source is there for readability and self-documentation, . But why does BASH_SOURCE hold the name of the executing script, when it is defined in man bash as an array of source filenames corresponding to shell functions? Aug 28, 2014 · I. profile. ' or 'source') and executing a file in bash? Ask Question Asked 13 years, 2 months ago Modified 4 years, 7 months ago Jul 30, 2020 · I've read that BASH_SOURCE should be populated with the name of the executing script (and it works!). 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 . Note that if bash is started as sh (e. 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 Jul 30, 2020 · I've read that BASH_SOURCE should be populated with the name of the executing script (and it works!). 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 a shell keyword that is supposed to be used like this: source file where file contains valid shell commands. The commands are identical. It looks like BASH_SOURCE is actually an array, so it's better to use its last element, via "${BASH_SOURCE[-1]}", as @gkb0986 explains here and as I show in my brand new answer here, so that it works when the script is called from within bash functions as well. 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 source is a shell keyword that is supposed to be used like this: source file where file contains valid shell commands. bash_profile, . works. profile on startup. 7. It is as if the commands had been typed in directly. , 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. Perl has long and short versions of many of its control variables for the same reason. 2025072101 gives empty list. These shell commands will be executed in the current shell as if typed from the command line. The solution is to "install specific version" under uninstall drop down menu to try some more stable not the latest version What is the difference between sourcing ('. exists because it is quick to type. 5. ' or 'source') and executing a file in bash? Ask Question Asked 13 years, 2 months ago Modified 4 years, 7 months ago In my ~/. Footnotes: Actually, the first one of . But why does BASH_SOURCE hold the name of the executing script, when it is defined in man bash as an array of source filenames corresponding to shell functions? 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 The original sh sourced . The source command is not required by POSIX and therefore is less portable than the shorter . g. What is the difference between sourcing ('. bash_profile first, but if that doesn't exist, it will source . Using source on dash does not work, only . Dec 20, 2024 · Based on your solving attempt log the reason can be in version of VS code Jupyter extension that periodically breaks this feature. bash_login, . source script This also sources the script. 2025051601 kernels are shown and 2025. e. . /bin/sh is a link to /bin/bash) or is started with the --posix flag, it tries to emulate sh, and only reads . source is not POSIX. E. profile See also: Bash Apr 4, 2015 · How can I automatically source a particular shell script when I open a terminal window by right clicking somewhere and choosing "open in terminal"? For example, every time I open a terminal I need Oct 14, 2017 · When I try to use source from the cron job (I have tried both directly in crontab and in a script called by crontab) it doesn't seem to work. . Yes, it is more work than just building and installing. I made a simplified version of my project to demonstrate the issue (including rsyslog for logging): Dockerfile: FROM debian:jessie # Install aws and cron RUN apt-get -yqq update Sep 27, 2016 · When the script is done, any changes that it made to the environment are discarded. source is a shell keyword that is supposed to be used like this: source file where file contains valid shell commands. script The above sources the script. I made a simplified version of my project to demonstrate the issue (including rsyslog for logging): Dockerfile: FROM debian:jessie # Install aws and cron RUN apt-get -yqq update source is a shell keyword that is supposed to be used like this: source file where file contains valid shell commands. for me 2025. bash will try to source . Any environment changes are kept. profile 1. 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 Sep 27, 2016 · When the script is done, any changes that it made to the environment are discarded. iqch0 ljn ulsmpi 1tw fh9 dcec qxu kutpr eyzh f3c