This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-30
Channels
- # announcements (4)
- # babashka (3)
- # beginners (5)
- # calva (20)
- # cider (12)
- # clj-kondo (7)
- # cljs-dev (2)
- # clojure (76)
- # clojure-uk (4)
- # clojuredesign-podcast (8)
- # clojurescript (18)
- # clojutre (1)
- # cursive (9)
- # data-science (27)
- # datomic (2)
- # fulcro (32)
- # graalvm (4)
- # jackdaw (5)
- # jobs (2)
- # joker (5)
- # lumo (20)
- # off-topic (18)
- # pathom (3)
- # shadow-cljs (18)
- # sql (5)
- # tools-deps (1)
- # vim (11)
Does anyone else have the issue that using "cider-repl-output-clear" doesnt clear the cider-repl buffer of output? (Emacs 26.3 , CIDER 0.22.0snapshot (package: <tel:201904191025|20190419.1025>), nREPL 0.6.0, Clojure 1.10.1, Java 11.0.5-ea)
Thanks, I bumped to the latest CIDER. I think when I use the cider repl interactively and then use it to eval from source code - cider seems to get confused abut the contents of the "cider-repl" buffer. And when I invoke the cider-repl-clear-buffer - it only clears part of the buffer...
So sometimes I eval things from source code, but once in a while I pop over to the cider-repl and type something directly. I guess I can just not do that.
I will try to only eval source code, and not enter code directly in to the "cider-repl" buffer .... and see how far that gets me.
is there a way to print strings in the *cider-result*
buffer such that carriage returns output as newlines?