Search results

Having to set an executable bit AND have a .command extension is very odd. The .command extension is for the GUI and the executable bit is for the GUI and the shell. Whereas in all WMs I have ever used, the kernel knows to interpret the file based on the "#!" macro as long as the execute bit...

I think there is a wrapper app you can use called "Platypus". I don't know how to use it, but you might find something in Google. I had a similar problem: http://macosx.com/forums/unix-x11/288667-gui-fights-kernel.html#post1387237

OK Here it is: 1. Create the script 2. Chnage the extension to .command 3. # chmod a+x myfile.command This will work through finder. And... If you don't want to see the shell window pop up use "Platypus" which gives it a wrapper. I don't know how to use it, but just in case...

Hi! If I create a script: #!/bin/sh cd /mydir ./runme This should execute the file "runme", but it brings up a text editor instead. The file attributes are read,write, and execute on both the script and the executable. If I click the file, it pops up in a text editor, and if I...