This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-03
Channels
- # aleph (1)
- # beginners (99)
- # boot (16)
- # cider (35)
- # cljs-dev (46)
- # cljsrn (7)
- # clojure (152)
- # clojure-austin (7)
- # clojure-dusseldorf (8)
- # clojure-italy (1)
- # clojure-uk (7)
- # clojurescript (3)
- # core-async (12)
- # css (8)
- # cursive (18)
- # datascript (2)
- # datomic (19)
- # defnpodcast (6)
- # duct (3)
- # editors (8)
- # emacs (8)
- # figwheel (1)
- # fulcro (20)
- # hoplon (18)
- # jobs-discuss (5)
- # lein-figwheel (1)
- # luminus (3)
- # lumo (19)
- # off-topic (15)
- # onyx (9)
- # parinfer (2)
- # planck (6)
- # portland-or (7)
- # re-frame (4)
- # reagent (7)
- # remote-jobs (1)
- # ring (6)
- # ring-swagger (4)
- # spacemacs (10)
- # specter (3)
- # unrepl (131)
Is there a way to print to standard error from Planck? So far I've gotten (.error js/console "error!")
to work but it's a tad ugly
@spinningarrow This immediately comes to mind: https://github.com/mfikes/planck/issues/452
@spinningarrow Without that, I wonder if (binding [*print-fn* *print-err-fn*] (println "foo"))
does the right thing
@spinningarrow That’s a fairly common approach in ClojureScript. See https://github.com/clojure/clojurescript/blob/9778b34d9e988a28c64133c4751d235bbbd3e966/src/main/cljs/cljs/js.cljs#L28 for example.
@spinningarrow This is also, for example, how analyzer warnings are sent to “stderr”: https://github.com/clojure/clojurescript/blob/9a54081d3e0ffab699ee2e58b2adc595918f7c2b/src/main/clojure/cljs/analyzer.cljc#L488
Thanks for the info and the quick reply! I'll look into those links