[MacPorts] howto/bash-completion modified

Rainer Müller raimue at macports.org
Sat Feb 23 04:09:13 PST 2013

On 2013-02-23 07:54, Lawrence Velázquez wrote:
> On Feb 23, 2013, at 1:50 AM, MacPorts <noreply at macports.org> wrote:
>> Page "howto/bash-completion" was changed by c1653169 at rmqkr.net
>> Diff URL: <https://trac.macports.org/wiki/howto/bash-completion?action=diff&version=8>
>> Revision 8
>> Comment: Add /opt/local/bin/bash to /etc/shells
>> Changes:
>> -------8<------8<------8<------8<------8<------8<------8<------8<--------
>> Index: howto/bash-completion
>> =========================================================================
>> --- howto/bash-completion (version: 7)
>> +++ howto/bash-completion (version: 8)
>> @@ -57,6 +57,8 @@
>>  1. Select "Command:" and enter `/opt/local/bin/bash -l`
>>  1. Close and reopen any terminal windows
>> +Add /opt/local/bin/bash to the file /etc/shells, otherwise it will be impossible to use AppleScript to tell Terminal to execute scripts (like 'osascript -e "tell application \"Terminal\" to do script \"echo hello\""').
>> +
> Is this accurate?

I did not believe this either and I just tried it out, but it appears to
be correct…

I thought the file /etc/shells only controls what you can set as a login
shell. Why does Terminal.app even check there if you tell it to execute
a command from AppleScript? It opens a new window running the default
command specified in preferences without problems, but the command
passed from AppleScript is not executed.


More information about the macports-dev mailing list