http://dev.clojure.org/jira This file is an XML representation of an issue en-us 4.4 649 25-07-2011 http://dev.clojure.org/jira/browse/NREPL-18 tools.nrepl <p>Not sure how this should be configured, but it would be nice if doing something like (println large-seq-here) would flush output automatically after some number of characters. This is so that output could stream constantly across the nrepl connection instead of waiting for the entire output to send as one message (assuming no manual flushes).</p> NREPL-18

Flush *out*/*err* after N characters

Enhancement Minor Closed Completed Chas Emerick Colin Jones Wed, 18 Apr 2012 23:01:45 -0500 Wed, 20 Jun 2012 23:14:33 -0500 Wed, 20 Jun 2012 23:14:33 -0500 0 1 <p>There is a precedent for this, in the sense that many output buffers have some fixed size, and they are flushed when that size has been reached (e.g. <a href="http://www.gnu.org/software/libc/manual/html_node/Flushing-Buffers.html">http://www.gnu.org/software/libc/manual/html_node/Flushing-Buffers.html</a>, <a href="http://docs.oracle.com/javase/6/docs/api/java/io/BufferedWriter.html">http://docs.oracle.com/javase/6/docs/api/java/io/BufferedWriter.html</a>)</p> <p>We had talked about potential worries / headaches, where users may get partial lines printed at a time. But after more thought about it, I'm thinking we may be OK: concurrent <b>out</b>/<b>err</b> writes can already interleave in interesting ways, and depending on the placement of (flush) calls (explicitly or implicitly) to make them more atomic is something I'd already have expected to be fragile. Maybe others will see things I don't, though.</p> <p>The implementation I have uses 1024 as the default, but that's pretty arbitrary. A less dynamic way of setting the limit would be also be fine with me, though since we're already in I/O-land, I'd assume performance isn't going to be bound by the dynamic var lookup.</p> <p>Any thoughts on this one? It would be great to be able to print big seqs incrementally.</p> <p>Sorry for the delay, this fell through the cracks.</p> <p>Looks good to me, except: can we make the "buffer size" an argument to the <tt>session</tt> middleware fn? That's where people will want to be able to customize it, if ever.</p> <p>Commit and close this at will. <img class="emoticon" src="http://dev.clojure.org/jira/images/icons/emoticons/smile.gif" height="20" width="20" align="absmiddle" alt="" border="0"/></p> <p>Done, thanks a bunch!</p> Global Rank Patch Code and Test