Hi, I just wanted to say thanks on the M-x clojure-install feature of clojure-mode! I like some others on this thread used to use clojure-mode sans SLIME, (because SLIME and the need to upgrade didn't seem worth the installation hassle). However last week I saw clojure-mode's M-x clojure-install mentioned and thought I'd give it a try... I have to say it worked flawlessly for me on Ubuntu... So thanks to Phil and everyone who made clojure-mode so great!
I'm not yet sure of all the features SLIME brings to the table above clojure-mode with an inferior-lisp buffer, but given that it *just worked* I see no reason not to use SLIME now that the install is painless and clojure 1.0 is out the door. One problem I do have with clojure-mode/clojure is managing the classpaths for clojure projects... It seems that the typical elisp config only has one variable (which is then shared across all clojure files) for specifying the classpath... Personally I'd like to maintain the required classpath with the project and outside of my .emacs files and was wondering if anyone had any elisp setups to work around this.... I was thinking maybe having clojure-mode search every directory up from the file your editing for a .classpath file to pass to a clj bash script for evaluation... How does everyone else do this? R. 2009/9/8 Phil Hagelberg <p...@hagelb.org>: > > Konrad Hinsen <konrad.hin...@fastmail.net> writes: > >> On 8 Sep 2009, at 02:36, Phil Hagelberg wrote: >>> However, now that clojure-mode has the M-x clojure-install command >>> that sets up SLIME etc, I don't know if the built-in subprocess >>> features are worth keeping around any more. Personally I have never >>> used them or heard of anyone using them; I wonder if they are just >>> legacy baggage. >>> >>> Would anyone be opposed to their removal? >> >> Until now I have never even looked at SLIME, considering the number of >> difficulties I see reported by lots of people. Life is too short to >> waste on configuration problems... and in that category I am still >> busy dealing with Clojure's move to github. I still use clojure-mode >> with its basic interaction commands for all my Clojure hacking. > > Most of these are caused by people manually installing SLIME rather than > using M-x clojure-install. I would rather focus on having one method of > subprocess interaction so we can make that work as smoothly as possible > than keep this vestigal functionality in here that only a handful of > people use. > >> On the other hand, if SLIME installation is painless now, that would >> be fine with me as well. > Please give it a try and let me know if you have any problems. M-x > clojure-install should pull in everything you need, including its own > copy of Clojure 1.0. > >> Clojure-update is a sensible complement to clojure-install, I'd >> strongly vote for keeping it. > > I think the value-add here is pretty minimal. Before Clojure 1.0 if a > change in Clojure broke swank-clojure, we'd have to scramble to get it > fixed in swank-clojure, and everyone would update. But now that there's > a stable target, I haven't been tracking master closely, so staying > up-to-date is much less important. > > Plus it's just a wrapper around a handful of shell commands. If more > people use it I may keep it around, otherwise I'd suggest switching over > to a shell script. > > -Phil > > > > -- Rick Moynihan http://twitter.com/RickMoynihan http://delicious.com/InkyHarmonics http://sourcesmouth.co.uk/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
