Re: Questions about channels

I just noticed you were actually using the exit code. In that case, you probably want something like (.on p "close" (fn [exit] (put! c [:exit exit]) (a/close! c)) Take care, Moe -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group,

Re: Questions about channels

On Wed, Jan 6, 2016 at 9:48 PM, wrote: > I'm using ClojureScript and nodejs and I'd like to spawn a child process > and deal with the result (stderr, stdout, exit code). > > Here's a short gist > showing an > approach that spawns the p

Re: Clojure eXchange 2015

If you don't have time to watch all the talks I wholeheartedly recommend watching Chris Ford's _Duelling Keyboards_ keynote. Best presented talk of the conference, IMO. He doesn't go into details about Clojure, but does go through some live coding and music making. Also, music theory. I also enjoy

Re: Questions about channels

Ah, I perhaps should be using node's spawnSync instead. But I'm still interested in what you think because perhaps in the future I might want to write a synchronous wrapper for some other js library which doesn't provide a sync alternative out of the box. On Wednesday, January 6, 2016 at 1:48:1

Re: org-mode Clojure babel

"0.11.0-SNAPSHOT". It's case sensitive. Reid On 01/06/2016 02:23 PM, Johannes Brauer wrote: > I tried this before. But with > {:repl {:plugins [[cider/cider-nrepl " 0.11.0-snapshot"]]}} > in my profiles.clj and cider-jack-in I get a Java exception: > Starting nREPL server via lein repl :headless.

Re: Pattern for service with multiple clients using two-way channels?

Most would perhaps start with the classic approach of having each request contain a :reply-to channel that the responses go into, but I think this is a mistake. IMO, there are two main ways of building systems with core.async 1) request/response. 2) dataflow graphs. I prefer the second approach w

Re: Pattern for service with multiple clients using two-way channels?

Let each request carry the callback channel. It is then the requestor's option to reuse a channel for multiple requests or to open one for each request or some combination. For example, some requests might get a lot of responses and the requestor may need to close the channel before getting the

Questions about channels

I'm using ClojureScript and nodejs and I'd like to spawn a child process and deal with the result (stderr, stdout, exit code). Here's a short gist showing an approach that spawns the process and routes all output to a channel. My go

Re: org-mode Clojure babel

I tried this before. But with {:repl {:plugins [[cider/cider-nrepl " 0.11.0-snapshot"]]}} in my profiles.clj and cider-jack-in I get a Java exception: Starting nREPL server via lein repl :headless... error in process sentinel: Could not start nREPL server: java.lang.IllegalArgumentException: Bad a

Re: org-mode Clojure babel

If you update to cider/cider-nrepl 0.11.0-snapshot in your .lein/profiles.clj that should fix the problem. On Wed, Jan 6, 2016 at 1:02 PM Johannes wrote: > BUT!!! > > With cider-nrepl set to 0.10.0 and cider set to 0.11.0-snapshot emacs > complains: > WARNING: CIDER requires nREPL 0.2.12 (or new

Re: org-mode Clojure babel

BUT!!! With cider-nrepl set to 0.10.0 and cider set to 0.11.0-snapshot emacs complains: WARNING: CIDER requires nREPL 0.2.12 (or newer) to work properly WARNING: CIDER's version (0.11.0-snapshot) does not match cider-nrepl's version (0.10.1). Things will break! That's not an org-bable problem,

Re: Reducing the pain of a clojars outage

Ouch. I'm not sure what happened to that email. I blame autocorrect. There were some scaling problems with npm in the past and they ended up taking funding. The list of issues you've provided look good. Perhaps some "newbie" tags in the issues would be good too. I will join the maintainers list.