Getting back to Phil Hagelberg's comment that maintaining a project's classpath in both a SLIME config and shell script for each project/ application is a "Don't Repeat Yourself" violation, there is a way to avoid that:
Don't bother with swank-clojure-extra-classpaths. Instead, include / path/to/swank-clojure in the classpath of each of your project's startup shell scripts. Each project starts up a swank server using something like the following in its initialization code, using a unique port for each project: (require 'swank.swank) (swank.swank/ignore-protocol-version "2009-01-01") (swank.swank/start-server "/dev/null" :port 7777 :encoding "iso- latin-1-unix") Connect to your running app from emacs by using "M-x slime-connect" rather than "M-x slime". When you're done, use "M-x slime- disconnect" (or from the REPL, "," then "disconnect") to leave your process running. In addtion, including swank in your running production app is a real benefit since you can connect to it from emacs at any later time for diagnosis, debugging, etc... -Craig --~--~---------~--~----~------------~-------~--~----~ 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 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 -~----------~----~----~----~------~----~------~--~---
