How to run Terminal commands from Finder?

Question

Level 2

170 points

How to run Terminal commands from Finder?

I would like to put a series of Terminal commands into a file, then run the commands by double-clicking on the file in Finder. I've found a number of sources on how to do this on the internet, but nearly all include comments from other users saying "this didn't work for me". I've not found a definitive "this is how to do it".

I created a test file using TextEdit, named it test.command, and saved it to my desktop. The file contains these commands:

!/bin/sh

chmod +x ~/Desktop/test.command

echo "hi there"

echo "hi again"

When I double-click on the file, however, it sometimes just opens in Finder. Other times, I get an error message saying that I do have permission to run the file. I thought the chmod command was supposed to handle the permission, but maybe I'm not using it correctly.

Can anyone help?

iMac, OS X Yosemite (10.10)

Posted on Feb 8, 2016 4:11 PM

Reply

Answer 1

BobHarris

Level 9

57,331 points

Feb 9, 2016 6:29 AM in response to pomme4moi

#!/bin/sh

you need the # followed by the ! as the very first 2 characters of the file.

And since bash is the default shell, you should most likely actually say

#!/bin/bash

The chmod +x command needs to be done after creating the test.command file, not inside of it.

Another way to execute shell commands is via Automator -> Run Shell Script

Automator does not need to open a Terminal session to process the commands. But if you want to have the command display something, it might be simpler to use a .command file, although there are ways to display things from an Automator app as well.

Reply

Answer 2

pomme4moi Author

Level 2

170 points

Feb 9, 2016 6:32 AM in response to BobHarris

Thanks BobHarris. Very helpful. So do I have to go into Terminal and run the chmod command every time I restart my Mac? Or will it remember the permission between restarts? I guess I'll find out when I next do a restart ...

Reply

Answer 3

BobHarris

Level 9

57,331 points

Feb 9, 2016 8:41 AM in response to pomme4moi

It is the file permissions. It is stored as part of the file metadata (the same as the name, the file size, the file owner, etc...). It is a one time thing. You are setting the execute permission so the operating system knows there is executable code inside, and not your grocery shopping list. Then again, maybe trying execute your grocery shopping list might be interesting 😀

Reply