cmd line?

It seems like the problem you are describing is more an aspect of Mac OS X
file structures. The easiest way to open any application from the terminal
(other than unix binaries) is to use the open command i.e. open
/Applications/Remote\ Desktop or more likely in a script open
"/Applications/Remote Desktop".

Since most mac apps are packages, with a binary hidden inside them you can
usually open them by the standard unix convention
/Applications/App.app/Contents/MacOS/App

The open command shortcuts this, doing the samething as a double click on
the app in the Finder. In this case you would simply call open
/Applications/App.app without the package contents listed out...

The open command is often necessary for non Cocoa apps since they often do
not have the above mentioned package structure.

Hope that helps clear things up, basically just use open and you'll always
be good to go. Please note that open is basically a double click (or
Command+O) in the Finder and can be used to open folders, documents,
applications ‹anything you can open from the Finder.

Errol Sayre



On 4/25/04 1:04 PM, in article BCB1CA58.1EB5F%trash@nospam.demon.nl, "Marco"
wrote:



 >
  >> I'm a mac neophyte, coming from the unix world.
  >> I tried installing ms rdc, by launching the downloaded .dmg file, and
  >> dragging its extracted folder into /Applications.
  >>
  >> I'd like to script rdc; I'm used to writing Bourne Shell Scripts.
  >> However, when I launch terminal, then do
  >> cd /Applications/Remote\ Desktop/
  >> ./Remote\ Desktop\ Connection
  >> I get an error, essentially, that the rdc binary is only a header.
  >>
  >> How do I run rdc from the command line?
  >> Am I required to use OSAscript or AppleScript?
  >> Can I pass a hostname, such as 'localhost' or '127.0.0.1' to rdc?
 >
 > You can create a profile in RDC and save it. If you create an Applescript
 > which launches that profile it will work just fine :)
 >
 >> Stay informed about: cmd line?