|
|
Harumph!
Not only is this what Terminal was invented for (I keep a little 20x4 terminal window up all the time) our gracious host once published a script I wrote for automatically mapping all applications to aliases:
---
Harumph!
Or "source" the example init files. My ~/.cshrc file contains:
Harumph!
That would work - but this way Applescript finds the application - you don't have to map aliases of type in full path names - Applescript will find the application (even if it is only on a removable disk or network volume I believe)
Harumph!
I don't think you realize what the scripts I mention do - they find all the apps automatically and build the aliases, automatically. You don't even have to add them to the script - any file ending in ".app" is found and an alias is built for it. My current alias files include 141 applications, from "addressbook" to "zinioreader". I didn't type in one of them.
Harumph!
I think it's clear that launching MacOSX apps is /not/ what the Terminal was invented for, or you wouldn't have to resort to massive alias creation in order to make it usable for that purpose. This script is a much cleaner way of quickly making all your applications accessible than anything that requires bringing up the Terminal.
Harumph!
How is making aliases a "resort"? It's what they're for. Add in autocompletion and I can launch any app by just typing the first few letters. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments 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.05 seconds |
|