Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 beta 3/9/83; site hplabs.UUCP
Path: utzoo!linus!decvax!harpo!seismo!hao!hplabs!kdp
From: kdp@hplabs.UUCP (Ken Poulton)
Newsgroups: net.unix-wizards
Subject: Re: stdio buffering considered harmful
Message-ID: <1630@hplabs.UUCP>
Date: Mon, 25-Jul-83 14:34:08 EDT
Article-I.D.: hplabs.1630
Posted: Mon Jul 25 14:34:08 1983
Date-Received: Tue, 26-Jul-83 07:23:23 EDT
Organization: Hewlett Packard Labs, Palo Alto CA
Lines: 14

Yes!  I remember interactive pipelines and they were very useful
at times.  'cat -u' is certainly a kluge, and an environment 
variable does seem like the right way to control stdio buffering.  
Note that environment variables need not be set at all unless 
you wish to change from the default buffering.

I guess I would set up an alias to do the environment setting, so
I could make a pipe run interactively with less typing:
          % ip m4 | adb
One might even consider having the shell set that environment
variable for you whenever the final STDOUT came to the terminal.

                                    Ken Poulton
                                    ...!hplabs!kdp