Ask Different is a question and answer site for power users of Apple hardware and software. It only takes a minute to sign up.
Sign up to join this community
For some reason, I cannot get AppleScript's "do shell script" to use the latest (GPLv3) Bash:
do shell script "/usr/local/bin/bash; echo $BASH_VERSION"
-- Result: "3.2.57(1)-release"
Strangely, it does work with an external .sh script:
#!/usr/local/bin/bash
echo $BASH_VERSION
Calling it like:
do shell script "~/Library/Scripts/Script.sh"
-- Result: "5.0.17(1)-release"
What's the difference and can I get it to work inside the .scpt script as well?
do shell script always uses /bin/sh, even if your default shell, shebang, or $PATH variable is set to something else.
To force it to use a different shell, you will need to call that shell. To run a command in bash, use the argument -c:
/usr/local/bin/bash -c 'echo $BASH_VERSION'
If you only want to run a single bash script, you can omit the -c with: /usr/local/bin/bash /path/to/script.bash
In AppleScript:
do shell script "/usr/local/bin/bash -c 'echo $BASH_VERSION'"
The man page entry for bash -c:
-c command_stringIf the -c option is present, then commands are read from the first non-option argument command_string.
do shell script "set" just by itself to see what's available by default when shelling out.
Apr 26, 2020 at 20:17
do shell script "/bin/tcsh my-command-file-path" (from an Apple doc), which made me think that it works the same for direct commands. Isn't the shell specifier redundant to begin with if you use a shebang in the external script file?
/bin/sh instead of treating the script like an executable. If you want to run only a bash script (not a command) you can just use do shell script "/usr/local/bin/bash /full/path/to/script.bash"
Apr 26, 2020 at 21:53
do shell script "~/Library/Scripts/Script.sh" right? I'll probably go for that option.
chmod u+x.
In your shell scripts, you should use #!/usr/bin/env bash.
Why?
It will use the bash that you've specified in your $PATH because the /bin/bash may be entirely different than the bash in /usr/local/bin/bash that you installed after the fact.
To ensure that you "get" the correct bash version, make sure that it's directory precedes the original in your path statement. For instance, if it's located in /opt/local/bin, your path may look something like this:
/opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
/etc/paths with /usr/local/bin as the first line.
echo $BASH_VERSIONin the sub shell you created. Whereas the scripts have the she-bang that specifies exactly which shell to execute the code in.do shell script "echo $PATH" and see if it has the new values before logging out and then again after logging back in.