Thanks Mark. I can confirm that the slime function slime-redirect-inferior-output fixed the problem. Now I see the expected output from the new thread within the same slime buffer.
-Alen On Sun, May 31, 2009 at 9:28 PM, Stephen C. Gilardi <squee...@mac.com> wrote: > > On May 31, 2009, at 1:00 PM, Mark Engelberg wrote: > >> I posted about this recently. In emacs/slime, printed output on other >> threads does not appear. I have not found a workaround, other than >> running such code in a standard REPL. > > > The output is ending up in the *inferior-lisp* buffer. > > This message from Bill Clementson: > > http://groups.google.com/group/clojure/msg/97037b8794ccd0a4 > > mentions the slime function: > > slime-redirect-inferior-output > > that redirects output from *inferior-lisp* to the slime repl buffer. > > I tried Alen's example after changing my slime setup to include a > slime-connected-hook along the lines of what's shown in Bill's message: > > (add-hook 'slime-connected-hook > (lambda () > (slime-redirect-inferior-output))) > > and it works: > > ; SLIME 2009-05-28 > user> (def foo 10) > #'user/foo > user> (.start (Thread. (fn [] (println foo)))) > 10 > nil > user> > > --Steve > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
