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

[Eli Zaretskii]

[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.

> anyways obviously something should be done in order to usefully see
> the output.

You can press C-j (or LFD, if your keyboard has that key), then the 
result is inserted into *scratch*, where the one-line limitation doesn't 
exist.