Here are Marty Hall's notes on capturing Lisp output:
-----------------------------------------------------


As a reminder, here are three possible methods for capturing
the results of an interactive session:

(A) Lisp-specific way: DRIBBLE.

> (dribble "Output.text")
This will tell Lisp to send a copy of everything you type and
everything the system types to the file Output.text. Now
just interactively enter your test cases. If you make errors,
please edit the Output.text file and remove those cases --
I don't need to see output of you going into the debugger.

> (dribble)
This call to DRIBBLE without a filename tells Lisp to *stop*
recording a copy of the session.

(B) UNIX specific way: script.

% script Output.text
This will tell UNIX to send a copy of everything you type and
everything the system types to the file Output.text. Now
just interactively enter your test cases. Again, if you make errors,
please edit the Output.text file and remove those cases --
I don't need to see output of you going into the debugger.
Also, UNIX traps ALL the characters. So if you have a typo and then
correct it on the screen, the file will have the original characters
and then some backspace characters, and then the correction
characters. Sometimes this makes the printout look poor.

% ^D
Hitting Control-D tells UNIX to stop recording a copy of the session.

(C) Emacs-specific way.

I strongly recommend running Lisp within a UNIX buffer. See the
section in the emacs handouts on Lisp-specific commands to see the
advantages. One of these advantages is that the Lisp buffer, like all
emacs buffers, can be saved to disk (Use C-x C-w to save it with a new
name such as Output.text), edited, etc. So run your test cases, save
the Lisp buffer, then if needed edit out any early lines that were not
test cases. 


In all cases, just print the file afterward. I think "enscript" looks
pretty good for printing.