Details
-
Type:
Enhancement
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
Description
Basically, (send-off some-agent println) & co. should get what's printed to out in that agent's thread back to the nREPL client — not silently let it dump out to System/out.
Portal ostensibly does this well. Examine their approach, see if it is compatible with nREPL's objectives.
Ill-formed brain dump:
- multiplex new out's to System/out
- (still won't solve clojure.test/test-out content will disappearing into the ether when it's loaded when out is bound to an nREPL out; maybe we should ensure out is bound to System/out while code is being loaded?)
- optionally multiplex System/out and System/err
- optionally join multiplexed S/out and S/err, receive :stdout, :stderr msgs