Re: more than one-line minibuffer needed for eval-last-sexp output

[Andreas Schwab]

eliz@is.elta.co.il (Eli Zaretskii) writes:

|> [Still using a fake address, despite the many requests not to, do you?
|> What would it take to get you to respect those requests, I wonder?]
|> 
|> On 20 Jan 2001, Dan Jacobson wrote:
|> 
|> > OK, go to the *scratch* buffer, or most buffers actually.
|> > Type: auto-mode-alist ^X^E
|> > to do a eval-last-sexp on this rather long valued variable, or your
|> > favorite other long valued variable.
|> > 
|> > Notice that the minibuffer doesn't crack open to give you the several
|> > lines needed to display the value.
|> 
|> This is solved in the next version 21.1 which is now in pretest.

Except that you know must set eval-expression-print-length and
eval-expression-print-level to nil, otherwise the output will be truncated
as well.

Andreas.

-- 
Andreas Schwab                                  "And now for something
SuSE Labs                                        completely different."
Andreas.Schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg