On 07/04/2020 01.38, Istvan Gabor wrote:
On Tue, 7 Apr 2020 01:20:22 +0200, Carlos E. R. wrote:
On 07/04/2020 00.35, Istvan Gabor wrote:
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>
Bu this . . . . . . . . . . . **********************************
Is not clear at all. You do not say how or where is that data.
Because I do not know where that data is or how to refer to it. That was my problem.
Documentation ;-)
Now, when you say that
myscript.sh:
#!/bin/sh cat >file
works, it means that the programs provides the data to the script in its standard input "file". And that crucial information you did not say.
I did not say that because I did not know it. If I had known it, I wouldn't have to start this thread. Why is it so difficult to understand this? And why could Per understand right away what I meant?
He guessed right. He guessed right what the program was doing, not what you meant ;-) Others actually had the same idea and told you, but you did not understand. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)