How do I communicate back and forth with command line tools through their stdin and stdout?
"open process" seems right, but the dictionary says it only works on Linux.
"shell" isn't interactive, and mixes stdout and stderr.
Unix pipes
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
-
- VIP Livecode Opensource Backer
- Posts: 9823
- Joined: Sat Apr 08, 2006 7:05 am
- Location: Los Angeles
- Contact:
Re: Unix pipes
The Dictionary entry for "open process" shows icons for Mac, Win, and Linux, and works on all three.
Where did you read that it was for Linux only?
Where did you read that it was for Linux only?
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
Re: Unix pipes
Quoting from memory: on OS X open process can only be used to launch apps, nut Unix processes. Use get shell for that.
-
- VIP Livecode Opensource Backer
- Posts: 9823
- Joined: Sat Apr 08, 2006 7:05 am
- Location: Los Angeles
- Contact:
Re: Unix pipes
Thanks. I see that note now, but missed it originally because Linux and OS X are very different beasts.
What non-application process do you want to interact with? Maybe we can come up with some clever workaround while a request is submitted for this to the RQCC: http://quality.runrev.com/
What non-application process do you want to interact with? Maybe we can come up with some clever workaround while a request is submitted for this to the RQCC: http://quality.runrev.com/
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn