This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-08-11
Channels
- # admin-announcements (36)
- # beginners (1)
- # boot (267)
- # cider (19)
- # cljs-dev (12)
- # clojure (149)
- # clojure-austin (4)
- # clojure-canada (1)
- # clojure-czech (3)
- # clojure-dev (31)
- # clojure-japan (2)
- # clojure-uk (22)
- # clojurebridge (3)
- # clojurescript (314)
- # clojutre (18)
- # core-async (8)
- # cursive (4)
- # datascript (1)
- # datomic (27)
- # editors (2)
- # events (80)
- # hoplon (13)
- # javascript (2)
- # jobs (5)
- # ldnclj (12)
- # ldnproclodo (1)
- # off-topic (4)
- # re-frame (21)
- # reagent (87)
- # testing (13)
@alejandro: only the spinner task, but someone already claimed it
we do have plenty of beginner friendly tasks in general, though (https://github.com/clojure-emacs/cider/issues)
@enn: No. Why would you want something like this? Let me guess - you’re depending on some output ending up there?
@bozhidar Kind of. If the process dies unexpectedly, I’d like to be able to look at the output for clues.
see https://github.com/clojure-emacs/cider/pull/818 and friends for details
Hmm, after reading that ticket, it’s not clear to me what the desired behavior is or why the current behavior is a bug. But let me rephrase. I would like to capture the stdout of a Clojure process started using cider-jack-in
somewhere that outlives the process itself—a buffer, a file, I don’t care. Is this possible?
the fact that something ends up in nrepl-server
is the unfortunate situation I referred to
@bozhidar I haven't had a chance sorry feel free to reassign as I'm about to go back to school and have no free time.
if someone wants to tackle this important tasks, here it is https://github.com/clojure-emacs/cider/issues/709