This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-12-02
Channels
- # adventofcode (63)
- # announcements (21)
- # babashka-sci-dev (1)
- # beginners (24)
- # biff (2)
- # calva (78)
- # cherry (6)
- # clj-commons (3)
- # clj-kondo (7)
- # clojure (91)
- # clojure-austin (2)
- # clojure-bay-area (6)
- # clojure-denmark (1)
- # clojure-europe (45)
- # clojure-nl (1)
- # clojure-norway (16)
- # clojure-portugal (3)
- # clojure-uk (1)
- # clojurescript (20)
- # conjure (11)
- # datalevin (13)
- # datomic (5)
- # emacs (14)
- # etaoin (15)
- # events (7)
- # fulcro (9)
- # funcool (1)
- # honeysql (26)
- # joyride (4)
- # kaocha (3)
- # lambdaisland (2)
- # malli (7)
- # off-topic (22)
- # pathom (29)
- # portal (58)
- # practicalli (8)
- # rdf (25)
- # reagent (14)
- # sci (3)
- # scittle (37)
- # shadow-cljs (10)
- # slack-help (2)
- # spacemacs (7)
- # sql (7)
- # tools-deps (1)
- # xtdb (2)
Anyone have an idea why my spacemacs stopped popping to results buffers? Did something with window.el change, perhaps?
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
for example, cider eval pprint last sexp opens the *cider-result*
buffer but it doesn't pop into view
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 :))
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 #C0617A8PQ has ideas
my setup always goes to the cider error buffer even though i told it not to.