Further, there's quite a bit of overlap between the two (especially when it comes to file system operations). They're both interoperable: you can call a shell command from AppleScript with do shell script "command here" and you can call AppleScript code from the shell with osascript -e "AppleScript".
Shell scripts (you referred to bash) work better when talking to low-level system objects and Unixy stuff. (For instance, you can say tell app "iTunes" to play and it will, or tell app "Finder" to open the first file of the second window.) Do these two languages have overlapping or near-identical usage cases, despite Apple's later invention of AppleScript - or are they intended to be used with different scenarios in mind? A high-level overview as well as some specific examples would be appreciated.īoth shell- and AppleScripts can be used just about anywhere either is appropriate.ĪppleScripts work better when talking to apps and user-level system facilities.
I am vaguely cognizant of the vast array of tasks I can accomplish with Bash script, though of course the code for some more advanced ones can quickly become convoluted. My question is, are AppleScript and Bash script commonly used (indeed, should they be used) for disparate tasks and purposes on OS X. The syntaxes are clearly very different, with AppleScript having a pseudo-natural-language style. The latter is of course a direct consequence of OS X using the Unix "bash" shell, while the former is Apple's own innovation. On OS X Lion and indeed previous versions there seem to be two main options for scripting and automation in OS X: AppleScript and Bash script.
#Betterzip applescript mac os
I'm a long-time Windows "power user" and developer who has recently decided to move over to Mac OS X.
0 kommentar(er)
