[slime-devel] First Impressions

[Lynn Quam]

iain.little at gmail.com wrote:

> 
>  The problem is, slime puts the output in the minibuffer. (Ok, ilisp
>  can be set up to do this as well, but I have it disabled.)  Often I am
>  printing out a representation of a large enough data structure that
>  the output doesn't even fit in the available space.  Also, the way
>  that it disappears as soon as a key is pressed prevents me from
>  refering to it later after I have checked/tested something else.  The
>  obvious workaround is to copy/paste the sexpr into the repl buffer,
>  but I do this so often (at least on my current project) that this
>  would be a serious pain.
>  
>  For me, the ideal way for this to work would be for there to be a
>  variable that controls whether or not evaluation output goes to the
>  minibuffer or the repl (Or is there one already?  I put a bit of
>  effort into looking and couldn't find anything...).  A different
>  evaluation command (maybe: slime-eval-last-expression-in-repl) would
>  also work.

I completely agree.  It can be very useful for output from
eval-last-expression to go into the REPL buffer.

Another useful command would insert the output from
eval-last-expression into the current-buffer in the same manner as
slime-eval-print-last-expression does with the *slime-scratch* buffer.