Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!cs.utexas.edu!uunet!portal!cup.portal.com!FelineGrace
From: FelineGrace@cup.portal.com (Dana B Bourgeois)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Dealing with multiple scripting languages (was: Elinating t
Message-ID: <21387@cup.portal.com>
Date: 17 Aug 89 23:10:19 GMT
References: <1989Aug8.214011.3351@agate.berkeley.edu>
  <1989Aug14.015608.21854@agate.berkeley.edu> <4117@sugar.hackercorp.com>
  <21369@cup.portal.com>
Distribution: na
Organization: The Portal System (TM)
Lines: 15

One kludgy way to get a command like stack to act differently in
scripts and from the CLI would be to utilize the stderr and stdout
handles.  Now this is *real* kludgy but if "Your stack size is"
comes out of stderr and "stack <bytes>" comes out of stdout then
you kinda get what is needed.  Of course your CLI will fill up with
partial messages from the different programs in the pipe.  But I 
*said* it was kludgy.

I guess the better way would be to put that into the program as a
command line flag.  stack -l tells stack to skip the verbage and
just output 'stack <bytes> <cr>'.



Dana