On Feb 12, 2007, at 10:21 AM, Tim Jones wrote:
That's because you're running /bin/bash and then using writeline to send your command. What if you just execute the command directly with:
[ connect shell statements with semicolons ]
I've not looked into the issue with the exec'd bash output (I believe it has something to do with the possibility that bash thinks it no longer has an attached TTY) since it can be resolved by executing the command directly. Also, if you exec a long-term interactive command such as "mail" directly, the output doesn't get mangled like that.
Okay, so that works perfectly. There's just one problem - I need to be able to get intermediate results in the middle of all those statements, and modify the subsequent statements based on that. How would I go about doing that?
Thanks, Andrew Keller _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
