Hey, Collin. By "standard" REPL I mean "clojure.main REPL in JVM" - which worked fine. I don't think my issue has anything to do with Cursive's way of connecting to nREPL, but rather with nREPL itself, seeing as had the same problem in a terminal window running `lein repl`.
Terje On Friday, March 17, 2017 at 2:11:11 AM UTC+1, Colin Fleming wrote: > > Hi Terje, > > When you say the "standard" REPL in Cursive, are you referring to the "Use > nREPL in normal JVM process" option, or the "Use clojure.main in normal JVM > process" option? Obviously the first does use nREPL, but doesn't go through > lein - Cursive just runs a JVM process, starts a bare-bones nREPL server in > it and connects to it. If you haven't tried that option, it might be worth > trying to see if the issue is in nREPL or in lein. > > Cheers, > Colin > > On 17 March 2017 at 11:05, Terje Dahl <te...@terjedahl.no <javascript:>> > wrote: > >> UPDATE: >> I only just discovered: >> It *does* work as expected when I run it from the "standard" REPL in JVM >> (in IntelliJ/Cursive), >> And it *does* work as expected when I run it in my own "home grown" REPL >> stack. >> It does *not* work as expected when running it in any variant of nREPL - >> including: >> - Through IntelliJ/Cursive >> - In command-line via `lein repl` (which is simply nREPL) >> >> So I have a potential solution, (and a possible nREPL bug), but it would >> be valuable to understand the cause of the issue. >> >> >> >> On Thursday, March 16, 2017 at 10:24:21 PM UTC+1, Terje Dahl wrote: >>> >>> I am attempting to embed an nREPL server in my application (version >>> 0.2.12). Everything seems to work nicely, except I am not able to get any >>> out from print statements et al. Even the basic example on the README >>> "(time (reduce + (range 1e6)))" doesn't work for me: I do not get back the >>> map containing the :out, but I get the two remaining. >>> >>> After two days of studying the source code of tools.nrepl (including the >>> testing code), leiningen.repl, reply, and a myriad of things online, I am >>> getting rather frustrated. >>> >>> It seems to maybe have something to do with *out*, but I can't figure it >>> out. Any hints at debugging it will be much appreciated. >>> >>> Also, any resources for "tool makers" would be of interest. >>> >> -- >> You received this message because you are subscribed to the Google >> Groups "Clojure" group. >> To post to this group, send email to clo...@googlegroups.com >> <javascript:> >> Note that posts from new members are moderated - please be patient with >> your first post. >> To unsubscribe from this group, send email to >> clojure+u...@googlegroups.com <javascript:> >> 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+u...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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.
