A small clue, gleaned from a cider issue: This outputs to the repl terminal.
(future (.start (Thread. #(println "blah2")))) This output is captured by vim. (future (println "blah3")) Still no idea what's going on. On Wednesday, May 21, 2014 1:09:31 PM UTC-7, Brian Craft wrote: > > Still not able to track down stderr. Anyone know how this stuff works? > > Dumping *err* from a ring handler, running from jetty, I get > this: java.io.PrintWriter@1d9e436a. This will write to the repl terminal, > so long as I flush (wtf... stderr is buffered?). > > If I dump *err* from a future, I get this: java.io.PrintWriter@fa4b83c. > This is the same value I get if I eval (str *err*) in fireplace. Writing to > this PrintWriter doesn't output anywhere that I can find. I'm guessing this > is the channel used by fireplace to capture output and return it to vim. > > So, something is different in how *err* is set up, between the jetty > adaptor and a future? > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
