Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!husc6!yale!Ram-Ashwin
From: Ram-Ashwin@cs.yale.edu (Ashwin Ram)
Newsgroups: comp.emacs
Subject: Re: Playing with the minibuffer
Message-ID: <31949@yale-celray.yale.UUCP>
Date: 22 Jun 88 14:59:13 GMT
References: <8806201232.AA03336@marvin.cme.nbs.gov> <367.582840018@pebbles>
Sender: root@yale.UUCP
Reply-To: Ram-Ashwin@cs.yale.edu (Ashwin Ram)
Organization: Computer Science, Yale University, New Haven, CT 06520-2158
Lines: 23
In-reply-to: jr@PEBBLES.BBN.COM (John Robinson)

In article <367.582840018@pebbles>, jr@PEBBLES (John Robinson) writes:
> Stephe Leake  had a good idea:
> 
> > In DEC's LSE, _all_ messages (system broadcast, editor error messages,
> > etc) get _appended_ to a $MESSAGE buffer, which the user can edit as a normal
> > buffer. I find this _very_ useful for keeping track of what I'm doing,
> > since I usually seem to be doing several things at once (waiting for
> > something to compile or link, answering a mail message that just came
> > in, etc). It appears that this approach would satisfy the recent
> > requests for minibuffer string access.

It sure would... I think this is a great idea.  To do it right, however, it
would have to be written in C (shouldn't be that hard).  It would also be nice
to have a user variable to determine how many messages should be kept (or
perhaps how large the buffer could be, or how large the message ring should be,
or whatever) before the oldest messages were automatically purged.  This would
avoid massive buildups of the message buffer.

-- Ashwin.

ARPA:    Ram-Ashwin@cs.yale.edu
UUCP:    {decvax,ucbvax,harvard,cmcl2,...}!yale!Ram-Ashwin
BITNET:  Ram@yalecs