This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-06-13
Channels
- # beginners (36)
- # boot (1)
- # cider (4)
- # cljsrn (2)
- # clojure (137)
- # clojure-brasil (3)
- # clojure-czech (3)
- # clojure-italy (17)
- # clojure-nl (8)
- # clojure-spec (7)
- # clojure-uk (153)
- # clojurescript (84)
- # data-science (2)
- # datascript (13)
- # datomic (30)
- # editors (64)
- # emacs (22)
- # events (6)
- # figwheel (26)
- # fulcro (7)
- # hoplon (5)
- # jobs (5)
- # jobs-discuss (57)
- # keechma (3)
- # leiningen (4)
- # luminus (1)
- # midje (2)
- # off-topic (26)
- # portkey (18)
- # re-frame (4)
- # reagent (10)
- # ring-swagger (3)
- # shadow-cljs (135)
- # spacemacs (5)
- # sql (14)
- # tools-deps (125)
If anyone is interested there's a PR (https://github.com/clojure-emacs/cider/pull/2323) open to make eval-ing the top level defun do the correct thing inside of comment forms and eval the top level inside of the comment form rather than just dumbly returning nil from the comment itself. comment and thoughts welcome
@dpsutton no, I want to see the docment of .write
.
Hey all: does anyone know if it's possible to suppress the printing of errors directly in the cider repl, but still have them show in an exception pop-up buffer? The errors being printed directly into the cider repl are playing havok with the parenthesis parsing and indentation modules.