open -a /Applications/LWSN/LWSN
open "lwsn cmdline"
I dunno -- anything that involves using open(1) is probably not going
to yield satisfaction; at best you'll be able to start the application,
but control over the app will be lost.
AFAIK, once open(1) is used to run an application, the shell and the app
go their separate ways; the app 'forks off and away', becoming parented
to the WindowServer.
At that point the shell/rush will no longer have control over the process,
and the process pretty much becomes managed by the window manager.
Both reparenting and involving the window manager are two deal breakers;
command line apps should do neither to be apps managable by shell scripts.
In my experience, if an app can't be run from the command line unless
open(1) is used, it's not really a command line app, and shouldn't be
considered for use in shell scripts where controlled, serial execution
of programs is needed.
--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Cel: (Tel# suppressed)
Fax: (Tel# suppressed)
|