with-out-str assumes Unix line ends

2009-08-07 Thread Nathan Kitchen
Anne's recent attempt to start a new thread for this question seems not to have worked. I'd hate for her and ataggart to be frustrated by further back-and-forth over the identity of the thread he started, so I'm starting a new thread for her question. === begin content from Anne === Sorry for the

with-out-str assumes Unix line ends

2009-08-06 Thread Anniepoo
Sorry for the confusion - I read this list on an email feed. Turns out replying to a message from there and changing the subject isn't sufficient to start a new thread. Apparently it renames the thread. (suboptimal). original question: (use 'clojure.contrib.duck-streams) (spit "C:\\test.txt"

Re: with-out-str assumes Unix line ends

2009-08-06 Thread ataggart
Anne, please don't threadjack. Now my original subject appears missing, since you renamed it. On Aug 6, 1:03 am, Anne Ogborn wrote: > (use 'clojure.contrib.duck-streams) > (spit "C:\\test.txt" >     (with-out-str >       (println "foo") >       (println "bar") >       (flush))) > > On my XP Tab

Re: with-out-str assumes Unix line ends

2009-08-06 Thread Mike Hinchey
What does this return on Windows? (with-out-str (.println (java.io.PrintWriter. *out*))) If it's "\r\n", then maybe (newline) should be changed to print (System/getProperty "line.separator") instead of \newline as it does now. Thoughts? -Mike On Thu, Aug 6, 2009 at 1:03 AM, Anne Ogborn wrote:

with-out-str assumes Unix line ends

2009-08-06 Thread Anne Ogborn
(use 'clojure.contrib.duck-streams) (spit "C:\\test.txt" (with-out-str (println "foo") (println "bar") (flush))) On my XP Tablet OS computer results in a file with unix line endings. Is this proper behavior? --~--~-~--~~~---~--~~