Timeline for Simple, free GUI application for running shell scripts
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 22 at 2:32 | comment | added | David Anderson |
If you are hung up on chmod +x, then you might consider using source instead.
|
|
| Feb 21 at 20:01 | comment | added | Wowfunhappy | @dan I did it this way because I originally made the scripts for myself and I found it easier. I could change it to use arguments—but I think that worsens the problem for someone who hasn't used the Terminal before. | |
| Feb 21 at 18:04 | comment | added | athena | Why don't you use arguments passed to your shell scripts so as to avoid any need to edit them and thus any error? | |
| Feb 21 at 17:21 | comment | added | Graham Miln | See also How to make a Mac OS X .app with a shell script? | |
| Feb 21 at 16:50 | answer | added | benwiggy | timeline score: 1 | |
| Feb 21 at 16:36 | answer | added | Demis | timeline score: 0 | |
| Feb 21 at 15:23 | answer | added | Graham Miln | timeline score: 0 | |
| Feb 21 at 15:20 | answer | added | Graham Miln | timeline score: 0 | |
| Feb 21 at 15:12 | comment | added | nohillside♦ | It does, as depending on the distribution mechanism, the x bit will already be set. You could even send us a tar.gz for them to double-click | |
| Feb 21 at 15:10 | comment | added | Wowfunhappy | I created the script. I can email them, airdrop them, put them on a USB drive, etc—I haven't really thought about it, it doesn't really matter. | |
| Feb 21 at 15:10 | history | edited | Wowfunhappy | CC BY-SA 4.0 |
added 62 characters in body
|
| Feb 21 at 15:10 | comment | added | nohillside♦ | How does the script get created in the first place, how does it get onto the Mac of the user? | |
| Feb 21 at 15:07 | history | asked | Wowfunhappy | CC BY-SA 4.0 |