This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-19
Channels
- # aws (4)
- # aws-lambda (2)
- # beginners (67)
- # boot (38)
- # cider (32)
- # cljs-dev (12)
- # cljsrn (2)
- # clojars (2)
- # clojure (190)
- # clojure-chicago (1)
- # clojure-dusseldorf (2)
- # clojure-germany (1)
- # clojure-greece (3)
- # clojure-italy (5)
- # clojure-russia (6)
- # clojure-spec (47)
- # clojure-uk (10)
- # clojurescript (59)
- # cursive (9)
- # data-science (14)
- # datomic (24)
- # devops (16)
- # emacs (8)
- # fulcro (25)
- # graphql (30)
- # hoplon (123)
- # juxt (15)
- # lambdaisland (2)
- # leiningen (4)
- # luminus (6)
- # lumo (9)
- # off-topic (11)
- # om (7)
- # onyx (8)
- # re-frame (14)
- # reagent (5)
- # ring-swagger (5)
- # shadow-cljs (46)
- # spacemacs (41)
- # specter (8)
- # testing (8)
- # unrepl (31)
- # yada (18)
@gonewest818 I was installing from melpa
but I now tried to pin both projectile and helm-projectile to melpa-stable and installed 1.4
and it still goes bonkers
so don't really get what's going on
I finally sorted out why my cider repl wasn't pprinting (had to remove the whidbey plugin, obvious in hindsight).
Now I'd like to be able to C-u C-x C-e
to print the result of the preceding expression to the buffer (which it already does), but have it pprint instead of one giant line.
is that a feature or will I have to get my hands dirty to monkeypatch it in?
cider-pprint-eval-last-sexp
leaves the result in a popup buffer… I realize it’s not exactly what you asked but…
@gfredericks btw, I made some attempts at a cider-pprint-eval-last-sexp-to-buffer
in this gist, but ended up asking a question in #cider because it’s not working as I expect. https://gist.github.com/gonewest818/5f68a092994ba135d915bf14c807329f