|
|
AppleScript not so easy...
Download the script and open a Terminal window. Change the permissions on the script so that the script is executable. It seems you know how to get this far. The next step is to type at the command line ./NAMEOFSCRIPTwhere "NAMEOFSCRIPT" is the name of the script you made executable. The "./" is command line-ese for "run what comes next." Gabester is right, however. If you really want control over your Mac the most direct way is the command line. Because of this, many advanced techniques will specify command line interaction. If you've been around Macosxhints for any length of time, you almost certainly know this to be true. That said, yes, the command line is scary for most GUI-only users. There is a learning curve to the command line but--and this is an important but--it is very simple to get started on that learning curve. You can learn a lot in twenty minutes that will make your Mac OS life much easier (and richer and complex) by dipping a toe into the "mysterious" waters of the CLI (command line interface). The best way is to get experience in a UNIX shop. But since you are a professional and, as you say, "life is too short," there is a great batch of OS X command line tutorials at Macdevcenter.com. The first tutorial is a great place to start since it is designed to help beginning CLI users with a "step by step [of] how to get comfortable with the Terminal". Happy travels.
AppleScript not so easy...
Thanks, but I still can't make it work - here's the session (I tried it twice because I couldn't figure out how many slashes were needed)
Welcome to Darwin! grant-thompsons-power-mac-g5:~ grant$ chmod o+x /Users/grant/Desktop/scriptmtuI might have a look at those tutorials if I ever have time but frankly, I want to use my computer, not futz with its vitals. I started out in the era of punched cards and men in white coats and thought back then there must be a better way. I see neither charm nor virtue in the CLI. As I said I've only used it once before, following a hint from this site. At least it worked that time (though it didn't help...) Maybe one of you wizards can tell me why Msoft Windows Service Pack 1 breaks OS X access to servers - in exactly the same way it was broken when 10.4 first came out. I'm running 10.4.4. mount_smbfs: error from NetrShareEnum call: exception = 382312522
AppleScript not so easy...
>Maybe one of you wizards can tell me why Msoft Windows
AppleScript not so easy...
> The "./" is command line-ese for "run what comes next." |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:Hints1 new Hints in the last 24 hoursComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.09 seconds |
|