-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing stdout output #129
Comments
Interesting - now when you saw via vim-fireplace, does that mean you spin up a After not-yet-enough digging, I suspect what's happening is this: nREPL sets up session bindings for This experiment would seem to support that theory: user=> (doall (foo nil))
nil Hello, World!
Hello, Mars
Exception talking to many planets user/foo/fn--668 (NO_SOURCE_FILE:5) I opened an nREPL ticket in JIRA to track this: http://dev.clojure.org/jira/browse/NREPL-45 |
Replying here instead of on JIRA, because I cannot replicate this in at least one nREPL environment (cider). There, I get:
This is with Clojure 1.6.0-alpha3, nREPL 0.2.3, cider 0.6.0alpha (basically the current HEAD). FWIW, |
OK, I don't know much about cider but it does appears to set up some middleware (maybe it changes the forcing behavior?). I'll try and install it sometime soon and see what's happening there. Can you see why/how any |
OK, I got cider 0.6.0alpha (from Melpa - I tried Marmalade first but got 0.5.0), nREPL 0.2.3, clojure 1.6.0-alpha3, and I'm still seeing: user> (foo nil)
nil Hello, World!
Exception talking to many planets user/foo/fn--1208 (form-init8029966451087486244.clj:5) But! When I turn on @cemerick let me know what you think. |
Gah, you're right. Pretty-printing trolls me again. :-P Taking a second look at the proposed patch now. |
I think this stackoverflow thread sums it up pretty well as behavior is observed via lein repl (and indirectly via vim-fireplace):
http://stackoverflow.com/questions/20437767/what-happens-to-second-println-statement-clojure-repl?noredirect=1#comment30532207_20437767
Thanks.
Okay so its look like REPL-y tries captures the result of the whole expression first as this prints nothing for 15 seconds
(map (fn [x] Thread/sleep 5000 (println "x") x) [1 2 3])
Should ideally stdout buffer be flushed if an exception occurs like on vanilla clojure repl? Or would this side effect confiict with the idea of printing the result of the expression
The text was updated successfully, but these errors were encountered: