spacemacs

Ben Sless 2022-12-02T13:19:04.229149Z

Anyone have an idea why my spacemacs stopped popping to results buffers? Did something with window.el change, perhaps?

practicalli-johnny 2022-12-02T13:32:41.951739Z

Do you mean like Cider test report buffer? Or is this some sort of evaluation related buffer Assuming a package update and Spacemacs update (pull) before this issue occured Nothing jumps out at me from the Spacemacs commit history that seems related, could be a change in a package itself

Ben Sless 2022-12-02T15:48:34.120089Z

for example, cider eval pprint last sexp opens the *cider-result* buffer but it doesn't pop into view

practicalli-johnny 2022-12-02T17:44:05.743189Z

I've updated Spacemacs itself (without updating packages) and the eval pprint functions open in a *cider-result* buffer. I'll try update the 103 packages next :))

practicalli-johnny 2022-12-02T18:23:26.300889Z

I still get a *cider-result* buffer after updating to all the latest packages, pulling the latest Spacemacs code and updating Spacemacs configuration from template. I didnt see a config variable that could be set to change this behaviour. If its not fixed by an Emacs restart or Spacemacs update, then maybe #cider has ideas

Ben Sless 2022-12-02T19:17:02.223209Z

I recompiled Emacs and it behaves, now

👍 1
1
Drew Verlee 2022-12-04T16:17:27.704559Z

my setup always goes to the cider error buffer even though i told it not to.

Benjamin 2022-12-03T18:19:11.707429Z

maybe you have the result / error buffer open in another frame. This is a growth area for me as well, sometimes I would like it to pop more.

Ben Sless 2022-12-03T19:45:09.830789Z

It's been like that for a month