[slime-devel] [RfC] popping buffers up asyncly

[Tobias C. Rittweiler]

Helmut Eller <heller at common-lisp.net> writes:

> I think you are lumping together a few things here.  
> Displaying buffers and switching focus has not much to do with
> slime-eval-async.

They are related in so far as I'm mostly referring to popping up buffers
after some delay (i.e. after an async request returned from SWANK.)

I.e. I may want to C-c C-k --- which may take a short moment of time to
complete --, but I'd also like to do something in the meantime like
switching between Emacs frames. I still want the compilation notes
buffer be popped up in the frame I issued C-c C-k in.


> Often the result of the RPC is needed before we can decide to create a
> new buffer (unless we add a time travel feature).  E.g M-. only creates
> a buffer if there is more than one possible definition.

Well, M-. is done by a synchroneous request, so Emacs blocks and I can't
do anything in the meantime.


> I figure you bring up this issue because C-c C-c and friends pops up a
> buffer much more often then it used to.  Yes, that's annoying.

Yes, that's true, too. But C-c C-c is most often instantanenous so it's
not that bad because I'm not tempted to do anything in between.


Another scheme would be to _never_ pop up a new buffer, but introduce a
keybinding like C-c C-z which pops up the buffer created by the last
command, perhaps in a stack-like manner. A command which created a new
buffer in the background says so in the minibuffer.

  -T.