The version of slime I am using (20100404) doesn't define any
slime-redirect-inferior-output function.  Perhaps it has been renamed?

Steve

On Wed, Jun 2, 2010 at 1:06 PM, Karsten Lang <karstenl...@gmail.com> wrote:

> I don't suppose
>
> (add-hook 'slime-connected-hook 'slime-redirect-inferior-output)
>
> would work?
>
> On Tue, Jun 1, 2010 at 11:00 PM, Paul Hobbs <paul_ho...@hmc.edu> wrote:
> > I have a similar issue whenever I try to print anything from slime.
> > --
> > Paul Hobbs
> >
> >
> > On Mon, May 31, 2010 at 11:41 PM, Steve Molitor <stevemoli...@gmail.com>
> > wrote:
> >>
> >> When I run clojure-test-run-tests I can't see the intermediate test
> >> output.  Messages like the following flash by as the tests run:
> >>
> >>    error in process filter: Elisp destructure-case failed: (:write-
> >> string "Testing my-stuff"))
> >>
> >> I do see the final message: "Ran 3 test. 0 failures, 0 errors".  If
> >> there are failures or errors the offending lines are correctly
> >> highlighted in the source, but I can't see the error/failure message
> >> (these would have flashed by very quickly with the 'error in process
> >> filter....' messages).
> >>
> >> I think it's a problem with slime evaluation.  Clojure-test-mode calls
> >> slime-eval-async when the problem occurs.  I can cause the same issue
> >> when I manually run slime-interactive-eval ("C-c C-e") with the
> >> expression (clojure.test/run-tests).  The tests run but "error in
> >> process filter: Elisp destructure-case failed" messages fly by.
> >>
> >> I am using the test-is library.  I'm using GNU Emacs 23.1.90.1 with
> >> clojure packages that I installed today via ELPA.  (I installed
> >> clojure-test-mode, and its dependencies included clojure-mode, slime,
> >> etc.)
> >>
> >> Thanks,
> >>
> >> 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<clojure%2bunsubscr...@googlegroups.com>
> >> For more options, visit this group at
> >> http://groups.google.com/group/clojure?hl=en
> >
> > --
> > 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<clojure%2bunsubscr...@googlegroups.com>
> > For more options, visit this group at
> > http://groups.google.com/group/clojure?hl=en
>
> --
> 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<clojure%2bunsubscr...@googlegroups.com>
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
>

-- 
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

Reply via email to