Thanks Joe (and Simon and Frank).

Next question: How does the notion of an "app" in OS X map to the traditional idea of a process in unix.  Specifically, does an app still have stdin/stdout/stderr?  When I use 'open' on the command line, it appears to always fork the program call--is that baked in?

I'd like to get my hands on stdin/stdout/stderr of the main squeak process.  I've got Ian's OS X binaries and OSProcess seems to work (at least, the CommandShell works) although not all of tests pass.  But 'OSProcess helloWorld' doesn't print anything to the console that started squeak.

Pointers? Ideas?

Thanks,
david

At 06:43 PM 11/2/2004 -0500, you wrote:
>Using the "open" command should do the trick (i.e., "$ open 
>Firefox.app").  It's the same as double-clicking on the application's 
>icon.
>
>- Joe
>
>On Nov 2, 2004, at 6:17 PM, David Farber wrote:
>
>> I'm running Squeak3.7-MacOS-Full on my OS X 10.3 box.  Everyhing works 
>> fine when I click on the appropriate icons.  But I can't figure out 
>> out to run it from a command line.  The "executable" is an 
>> ".app"--which acts like a directory when I am at a command line.  So I 
>> can't find anyhting to execute.  Do I need a different vm?
>>
>> Thanks,
>> david
>>
>> --
>> David Farber
>> dfarber at numenor.com
>>
>
>
>
--
David Farber
dfarber at numenor.com