Re: open process

2019-09-28 Thread JB via use-livecode
Okay, thank you! JB > On Sep 28, 2019, at 11:25 AM, Dar Scott Consulting via use-livecode > wrote: > > I'm glad that was helpful. For me, when using open process as a background > shell is knowing when things are done. In my example, I can wait for > non-empty read results and then wait for

Re: open process

2019-09-28 Thread Dar Scott Consulting via use-livecode
I'm glad that was helpful. For me, when using open process as a background shell is knowing when things are done. In my example, I can wait for non-empty read results and then wait for a few empty read results. There is probably a better way. > On Sep 28, 2019, at 11:57 AM, JB via use-livecode

Re: open process

2019-09-28 Thread JB via use-livecode
It works for me too, Thanks Name Mtu Network AddressIpkts IerrsOpkts Oerrs Coll lo0 16384 82239 082239 0 0 lo0 16384 localhost ::1 82239 -82239 - - lo0 16384 127 localhost

Re: open process

2019-09-28 Thread Dar Scott Consulting via use-livecode
This works for me, LC 9.5 Mac. on mouseup set the cursor to watch put "netstat -i" into p put p -- flash open process p for read wait 1 seconds with messages read from process p until empty close process p put it end mouseup > On Sep 28, 2019, at 8:05 AM, JB via use-livec

Re: open process

2019-09-28 Thread JB via use-livecode
Thank you very much! That is what I suspected but I wanted to have someone clarify it for me. thanks again, JB > On Sep 28, 2019, at 7:46 AM, Paul Dupuis via use-livecode > wrote: > > passing information (arguments, commands, etc.) to another program using > "open process" requires that the

Re: open process

2019-09-28 Thread Paul Dupuis via use-livecode
passing information (arguments, commands, etc.) to another program using "open process" requires that the other program has a mechanism to listen to interprocess messages. Most programs designed to accept a set of command-line parameters do not have listeners for inter process communication (IP

Re: open process

2019-09-28 Thread -=>JB<=- via use-livecode
I provided the wrong path in the code by setting the default folder to desktop but the code has the correct path and do not set defaultFolder using desktop. The question is still the same about supplying the arguments to the executable. JB > On Sep 28, 2019, at 7:05 AM, JB via use-livecode > w

Re: Open Process, Interactive Shell on OS X

2016-02-28 Thread [-hh]
Each 'shell' opens it's own "terminal" session. You have to do your own housekeeping (stdin, stdout). Why don't you use (secure) sockets? ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and man