Path: utzoo!attcan!uunet!husc6!spdcc!ima!haddock!karl
From: karl@haddock.ISC.COM (Karl Heuer)
Newsgroups: comp.emacs
Subject: Re: Playing with the minibuffer -- two questions
Keywords: minibuffer
Message-ID: <4615@haddock.ISC.COM>
Date: 18 Jun 88 00:18:26 GMT
References: <31024@yale-celray.yale.UUCP> <2379@mipos3.intel.com> <25724@bbn.COM> <31464@yale-celray.yale.UUCP>
Reply-To: karl@haddock.ima.isc.com (Karl Heuer)
Organization: Interactive Systems, Boston
Lines: 16

In article <31464@yale-celray.yale.UUCP> Ram-Ashwin@cs.yale.edu (Ashwin Ram) writes:
>In article <25724@bbn.COM>, jr@bbn (John Robinson) writes:
>>[The minibuffer output is not visible to E-Lisp.  Why is this needed?]
>
>In order to be able to save a minibuffer message (e.g., a help message or an
>error message) in some way.  [E.g.] you want to look at the error message AND
>edit the offending source at the same time.

Also because the error message is sometimes too long for the minibuffer, and
it gets truncated.  "Wrong number of arguments: (lambda blah blah blah", and I
can't see how many arguments were actually passed.  For this, there should be
either (a) some way to retrieve the most recent minibuffer output, or (b) an
option for the minibuffer to automatically grow if a message doesn't fit.
(Perhaps minibuffer-max-lines, with a value of 1 being the current behavior?)

Karl W. Z. Heuer (ima!haddock!karl or karl@haddock.isc.com), The Walking Lint