Hi, On Thu, Mar 11, 2010 at 01:32:36PM -0800, Phil Hagelberg wrote:
> Historically this has been because calculating the classpath couldn't > be done in Clojure itself since it needed to be done before the JVM > booted. Having to figure this kind of thing out in a shell script or > in elisp is a headache if the rules are not simple. But now with the > subclassloader approach that lein and mvn use it's less of an issue. > But it would mean deprecating the pure-elisp swank launcher, and I > don't know how it would affect other tools (IDEs, etc), so I'm still > hesitant. I think this is a typical emacs misconception. Vim is an editor. Why should it have to know how a JVM classpath works? Setting this up is the responsibility of the developer. Put everything in lib/? No problem. Let maven/gradle/lein handle the classpath? No Problem. Have an esoteric shell script doing some voodoo incatations? No Problem. Putting this logic into the editor was the failure in the first place. Sincerely Meikel -- 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
