Fred Concklin <fredconck...@gmail.com> writes: > Clearly the solution is to turn off slime-highlight-edits. Although why > is slime bootstrapped on every jack-in?
Future versions will try to detect if it's already been bootstrapped and skip that step if so. But this functionality is still new, so I aimed for the simplest thing that could work. Also, it's targeted towards my workflow that creates a new Emacs instance for every project I'm working on and closes them when they're done. So in my case it's pretty rare for Emacs instances to outlive their slime sessions. I realize I'm in the minority on that, but hey--I'm the guy who implemented it, contributions welcome, &c. > The slime bundling and bootstrapping also seems to be overkill. Am I missing > something? It was motivated by the fact that 90% of the problems with slime revolve around "I can't get the damn thing installed". Bootstrapping from swank turns it into a two-step process, eliminating guesswork where people try to piece things together from outdated blog posts. I should note that if you've already got slime installed then the old instructions with M-x slime-connect still work fine! Don't feel a need to switch, since part of the motivation for jack-in was to reduce the amount of installation confusion. > I think the key issue is that slime integration with clojure-mode seems > to have global effects on all clojure files, which might not be the best > option. It would be great to have a clojure-enable-slime-if-in-current-project function to use as a hook instead of the naive clojure-enable-slime function. -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
