Mike K <mbk.li...@gmail.com> writes: > (add-to-list 'load-path "C:\\Program Files (x86)\\Clojure Box\\swank- > clojure") > > (require 'swank-clojure-autoload)
Sounds like you're using an old-ish version of swank-clojure; the autoloads are now generated automatically by elpa. >> Slime was designed for use with Common Lisp, which has a distinction >> between compiled and interpreted code. Clojure has no interpreter, so >> any way of loading in the code runs it through the compiler. > > Ah, OK. That explains the overload of the term "compile" I'll add a note to this to the swank-clojure readme. >> There are some features of Slime that have not been ported to Clojure >> yet and still only work in CL. Unfortunately the author of the Clojure >> port has dropped it and I am left maintaining it myself, and there are >> still several portions of the code that I haven't gotten a chance to >> dive into yet. > > Oh, so can you confirm that error navigation is basically broken? > Actually, I guess the relevant question is what CB 1.0's level of > functionality is. If I can get access to a machine without emacs > currently installed on it, I'll try to run the straight CB install and > see how it behaves. I wasn't even aware that the CL version provided error navigation here. But it looks like it shouldn't be too hard to fix now that you've made me aware of the problem. Note that in sldb (debugger) buffers pressing "v" on a stack trace frame will actually jump to the cause of the error if possible. -Phil -- 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
