Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Terminal | 67 comments | Create New Account
Click here to return to the 'Terminal' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Authored by: googoo on Nov 17, '06 08:26:19AM
I often use the terminal as a launcher. I have set up several aliases and scripts to open frequently used apps. For example, occasionally I run NetInfo Manager, but I do not use it often enough to take up room in the dock. I have the following entry in my .bashrc file.

alias netinfo='open -a /Applications/Utilities/NetInfo'

I just enter the command netinfo, and viola! No more drilling down to find /Applications/Utilities/NetInfo Manager in the Finder. I also use the command-line version of BBEdit to open text files more often than clicking on them in the Finder.


[ Reply to This | # ]
Authored by: kevinmontuori on Nov 17, '06 04:15:39PM

I'll second open(1) as a great all purpose launcher. In terminal open <filename> generally does the right thing, even with directories. From shell scripts and (especially) emacs, it's really handy. Back in the Sun, AIX, then Linux days, it was necessary to supply a "helper application" for each mime-type. Now open suffices for all of them. Swanky.

Other than that, I use Spotlight. I've tried quicksilver and got fed up when they required up-to-date checks for beta versions. That's crap.

[ Reply to This | # ]
Authored by: tirerim on Nov 27, '06 02:22:27PM

Yep, I do that for some applications. Finder/Dock and Spotlight for some others.

Of course, many of the applications I use don't even need to use the <code>open</code> command, since they just run in the terminal window. :-) (Favorites are ssh, emacs, irssi, yafc, and less.)

[ Reply to This | # ]