Les,

sorry, my iPad makes dots and colons difficult to see. The Rexx pseudo 
filenames always end with a colon, hence they are: stdin:, stdout: and stderr:

Regards

---rony

Rony G. Flatscher (mobil/e)

> Am 12.09.2016 um 22:12 schrieb Rony <rony.flatsc...@wu.ac.at>:
> 
> Hi Les,
> 
> this is standard Unix pipelining that was then implemented on DOS/Windows 
> (and OS/2) as well: each process gets three standard file handles assigned 
> with the same file descriptor (fd), which is 0 for standard input (known as 
> stdin, usually the keyboard), 1 for standard output (stdout, usually the 
> screen  and 2 for standard error output (stderr, usually the screen).
> 
> If you invoke a command on the shell you can redirect the input and output, 
> eg like
> 
>   Redirecting stdout to a file: 
>         cmd > out.txt
> 
>   Refirecting stderr to a file:
>          cmd 2> err.txt
> 
>   Redirecting stdin to get the entries from a file:
>          Cmd < input.txt
> 
>   One can combine these in any combination, also eg:
>           cmd < input.txt > out.txt 2> err.txt
> 
> In addition one can redirect the stdout file to be the stdin of a following 
> command using the pipe character | like
> 
>         cmd1 | cmd2
> 
> Whatever cmd1 writes to stdout will become the stdin input ofhe following 
> cmd2. 
> 
> There are quite a few articles and tutorials on the web.
> 
> ---
> 
> In Rexx the say statement writes to stdout; one can use the pseudo filename 
> "stdout:" in the lineout or charout BIFs. The stderr pseudo filename in Rexx 
> is called "stderr" and for stdin the pseudo filename is called "stdin".
> 
> In addition ooRexx provides the environment symbols ,input for .stdin, 
> .output for .stdout and .error for .stderr.
> 
> ---rony
> 
> Rony G. Flatscher (mobil/e)
> 
>> Am 12.09.2016 um 12:01 schrieb Les Koehler <vmr...@tampabay.rr.com>:
>> 
>> Rony,
>> 
>> By what magic does that become input to yad?
>> 
>> Les
>> 
>>> On 9/12/2016 5:55 AM, Rony wrote:
>>> Leslie,
>>> 
>>> usually a plain say-statement suffices, as it writes to stdout. If you need 
>>> tderr then use the .error monitor like:
>>> 
>>>    .error~say("some error information")
>>> 
>>> HTH
>>> 
>>> ---rony
>>> 
>>> Rony G. Flatscher (mobil/e)
>>> 
>>>> Am 11.09.2016 um 06:27 schrieb J. Leslie Turriff o <jlturr...@mail.com>:
>>>> 
>>>>  In the Linux terminal environment, there is a common paradigm for feeding
>>>> data into a command.  Two examples from the yad* man file are:
>>>> 
>>>>  Show search results in a list dialog with the title 'Search Results' and 
>>>> the
>>>> text 'Finding all header files...'.
>>>> 
>>>>  find . -name '*.h' | yad --list --title "Search Results"  --text "Finding 
>>>> all
>>>> header files.." --column "Files"
>>>> 
>>>>  Display a progress dialog while searching for all the postscript  files in
>>>> your home directory
>>>> 
>>>> find $HOME -name '*.ps' | yad --progress --pulsate
>>>> 
>>>>  I would like to use yad to display the output from my ooRexx programs, but
>>>> it's not clear how that could be accomplished.  Can anyone here suggest a
>>>> method?
>>>> 
>>>> Leslie
>>>> 
>>>> *yad is Yet Another Dialog tool for displaying information in a GUI window.
>>>> --
>>>>      A Caution to Everybody
>>>> 
>>>>  Consider the Auk;
>>>>  Becoming extinct because he forgot how to fly, and could only walk.
>>>>  Consider man, who may well become extinct
>>>>  Because he forgot how to walk and learned how to fly before he thinked.
>>>> 
>>>> -- Ogden Nash
>>>> 
>>>> ------------------------------------------------------------------------------
>>>> _______________________________________________
>>>> Oorexx-users mailing list
>>>> Oorexx-users@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/oorexx-users
>>> 
>>> 
>>> ------------------------------------------------------------------------------
>>> _______________________________________________
>>> Oorexx-users mailing list
>>> Oorexx-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/oorexx-users
>> 
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Oorexx-users mailing list
>> Oorexx-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/oorexx-users
> 
> 
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are 
> consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
> J-Flow, sFlow and other flows. Make informed decisions using capacity 
> planning reports. http://sdm.link/zohodev2dev
> _______________________________________________
> Oorexx-users mailing list
> Oorexx-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-users


------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. http://sdm.link/zohodev2dev
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users

Reply via email to