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

Click here to return to the 'Automatically create app-launching aliases in bash' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Automatically create app-launching aliases in bash
Authored by: vtron on Jul 13, '06 04:58:19AM
A small but crucial technical problem with the matching part of the script (the most uptodate version concerns applications without the .app extention.
For instance /Applications/GraphicConverter/GraphicConverter will turn into :
alias applications=open -a '/Applications/GraphicConverter'
which is clearly not what we want V

[ Reply to This | # ]
Automatically create app-launching aliases in bash
Authored by: porkchop_d_clown on Jul 13, '06 05:40:55AM

Good points;

I was thinking about that the other night - including how I don't think ".dock" applications exist any more; but you're wrong about graphic converter - that particular awk statement is used for building the alias name, not the application name.

For example, from my aliases:

alias adobephotoshopelements2="open -a '/Applications/Adobe Photoshop Elements 2/Photoshop Elements 2.0'"

And that works fine.

But you're right about finding too much with this - despite the search restrictions, it seems to be finding extra copies of applications that aren't in the specified directories, it also seems to do some weird things like this:

alias silverkeeper1.1.3="open -a '/Applications/SilverKeeper 1.1.3/SilverKeeper'"

alias silverkeeper1.1.3="open -a '/Applications/SilverKeeper 1.1.3/SilverKeeper ReadMe'"

Which is obviously bad. SilverKeeper Readme *is* an application, apparently it launches the Help file for SilverKeeper.

Everyone loves a clown, but no one will lend him money!

[ Reply to This | # ]