> From <centralsparc.CS.Berkeley.EDU at excl-forum-request> Tue Oct  7 00:32:57 1997
 > Date: shell\r\elogin:, 6 Oct 1997 22:04:40 -0800
 > To: <mickey at dryan> (Daniel Ryan), <cs.berkeley.edu at allegro-cl>
 > From: <n-a-n-o.com at kr> (kr)
 > Subject: Re: xemacs lisp listener buffer max size
 > 
 > At 13:45 10/6/97, Daniel Ryan wrote:
 > >Does anyone know how to limit the buffer size
 > >of a lisp listener when allegro is run from
 > >inside xemacs?
 > >
 > >Ideally this would be as simple as being able
 > >to set some max number of lines X to be saved
 > >such that the oldest are discarded as new
 > >output is sent by lisp and displayed at the
 > >bottom of the buffer
 > 
 > why would anybody want to do something like that ?? the great thing really
 > is that all the output is saved in an emacs buffer, in contrast to a stupid
 > xterm.
 > (though it helps to occasionally exit the lisp image and kill the
 > *common-lisp* buffer anyway to start over again, after you have accumulated
 > tens of MB of crud.  :-)
 > 
 > Greetings
 > Markus Krummenacker

Exactly the problem.  We have an application that must run continuously
for *months* while still displaying output to the buffer (thus we 
can't completely turn off output), yet not eventually die because 
a buffer fills up.

- Dan