Shell command doesn't give feedback until done

[Brian Yennie]

Agh, sorry- I obviously missed the point of the thread.

Add an ampersand after your command:

get shell("mycommand > mylogfile.log &")

Voila, a "backgrounded" process that returns immediately.

HTH,
Brian

> But that still won't return until mycommand is finished.  The 
> advantage of "start" in Windows is that you can use it to spin off 
> another app or even another shell.
>
> I have some vague memory of using some fancy punctuation in some unix 
> shells to start a process but not wait until it finishes, but that 
> must have been over a month ago, because I can't remember how that 
> goes.  I have a book here that might help, if I remember where I put 
> it.  In any case, I wasn't able to do what I wanted with shell(), that 
> is, to have shell() return right away.  Hmmm.  I may have been working 
> with pipes and that complicated what I was doing.  I now use an 
> external.