"Steven E. Harris" <s...@panix.com> writes: > In the meantime, I'll continue the investigation.
And yet more information: Apparently it's not critical to call on the RuntimeMXBean#getName() method specifically to kick the Swank thread out of its blocking call; just about /any call on a Java method/ from the Clojure REPL will unblock the Swank thread and make the connection complete. For example, I've tried calling java.util.concurrent.Executors#newSingleThreadExecutor() java.util.Collections#emptySet() java.lang.Math#max() and both work to unblock the Swank thread, but this one does not: java.lang.Integer#parseInt() Now get this: Right before the SLIME-Swank connection completes, Emacs beeps and prints the following two lines in the *Messages* buffer: ,---- | error in process filter: cond: etypecase failed: defun, (number cons string) | error in process filter: etypecase failed: defun, (number cons string) `---- Those errors messages come from the ELisp evaluator. Strangely, I can't find any etypecase or typecase form in file slime.el that tolerates all three of those types (number, cons, and string), so it's hard to figure out where the error is arising. -- Steven E. Harris -- 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
