Path: utzoo!attcan!uunet!zaphod.mps.ohio-state.edu!usc!ucsd!ucbvax!bloom-beacon!eru!hagbard!sunic!news.funet.fi!ra!rosenber
From: rosenber@ra.abo.fi (Robin Rosenberg INF)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Help! Need LOGFILE utility!!
Message-ID: <399@ra.abo.fi>
Date: 26 Oct 90 21:38:26 GMT
References: <10007@milton.u.washington.edu>
Organization: Abo Academy, Finland
Lines: 29

In article <10007@milton.u.washington.edu>, dsheythe@milton.u.washington.edu (Donald Sheythe) writes:
> For our CS assignments, our professor was kind enough to let us use
> Modula-2, so I decided to use my trusty Benchmark compiler.

Here they *force* us to use Modula-2.

> However, the assignments require a log of the program actually running.
> 
> It's an interactive CLI program and I can redirect the output to a file,
> but I can't see what I'm doing.  All the output goes to the file.
>
> What I need is a program (or shell) that will capture all CLI input/output 
> so I can see the output and get all of it recorded at the same time.
> 
> On the VAXen, this is really easy to do.  All you gotta do is type 
> the commands STARTLOG and STOPLOG.

Run the program from a script file.

echo >pipe: noline	; Looks stupid, but is necessary to make sure we
type pipe:		; don't accidentally get TWO instances of pipe:
run tee <pipe:a logfile	; Tee copies stdin to stdout and to the file
myprog >pipe:a		; Runs our program, output goes to the pipe

Tee is trivial to write yourself and pipe: is included with 1.3. Since
your program is interactive, make sure tee copies input to output character
by character, use AmigaDOS IO for that.

	Robin