![](https://seccdn.libravatar.org/avatar/1f3136209abe5c23eb73ad942f8e646a.jpg?s=120&d=mm&r=g)
On Mon, 6 Apr 2020 17:19:58 -0400, Anton Aylward wrote:
On 06/04/2020 07:18, Istvan Gabor wrote:
Hello:
I have a program that can send its output to a script.
Now that's an ambiguous phrasing if ever I met one!
Looking it at again, I guess you're right. That's because I did know what terms to use to describe it. I could have written my example like this: Program calls myscript.sh -option -option An myscript.sh runs as: myscript.sh -option -option <the-data-provided-by-the-program>
As an old UNIX hacker the idea of a set of pipes&filters is natural enough ... find ... -print0 | xargs -0 ... | grep <parameters> | awk '{format ..}' comes naturally. But the kernel support for that as copocesses doesn't exist in MS-DOS or VMS even if the CLI permits that syntax.
I even can't guess what the above is about.
Is that what is meant by "can send its output"?
No. What I meant was that the program sends/provides data (output) to the script it calls. The script should work with that data. That is the program's output is "piped" to the script's input. Thanks! Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org