On Nov 17, 8:43 pm, "Bill Clementson" <[EMAIL PROTECTED]> wrote:
>
> Rather than ask someone to assemble a package and post it for you, it
> is usually nicer (and a better learning experience) if you list
> exactly what you did, and post the minimal config scripts that you the
> tried out and which illustrate what didn't work for you.
I think you miss the point here. I'm suggesting that all new users
would be much better served if clojure.org site cached a combination
of the necessary elements of a working slime install, not that someone
post something for me alone.
The alternative is that new users end up chasing their tails because
several of the necessary elements are moving targets. The concept of
an actual stable release seems to be missing in the slime world as
well, and I'm not the only experienced lisp user to have voiced
misgivings about this state of affairs:
<http://groups.google.com/group/comp.lang.lisp/msg/793b201a4ad3fb80?
hl=en>
Stumbling over regressions among multiple continually moving targets
is not a "learning experience," it is merely an excercise in
frustration. This is why projects have releases. Then other projects
can build against those releases, and combinations of multiple
interdependent projects can have known working versions.
Where such releases are not available the next best thing is to grab a
known working combination and cache it. Pointing at the continually
shifting sands of multiple repositories is a really good way to ensure
that only the most persistent and experienced will stick around very
long. One could cynically suggest that this is desirable, but I
actually believe that the clojure community does not want to drive
away newcomers (after all, look at the volume of excellent
documentation). Simply caching a set of known working components would
completely eliminate this issue.
> However,
> since I recently upgraded to the latest Clojure, I'll share what
> worked for me:
>
> 0. Delete (or move away) any old versions of the following (e.g. don't
> assume that something you downloaded a couple of days ago is ok to
> use)
> 1. Download latest Clojure from
> svn:http://sourceforge.net/svn/?group_id=137961
> 2. Download latest clojure-mode & swank-clojure from
> git:http://github.com/jochu/
> 3. Download latest slime from cvs:http://common-lisp.net/project/slime/
> 4. Download latest clojure-contrib from
> svn:http://sourceforge.net/svn/?group_id=223136
> 5. Use ant to build clojure and clojure-contrib
> 6. Create a shell script (called "clojure") to launch clojure and put
> it in your PATH :
>
> #!/bin/sh -e
> java -server -cp /Users/bc/lisp/clojure/clojure/trunk/clojure.jar:\
> /Users/bc/lisp/clojure/clojure-contrib/trunk/clojure-contrib.jar:\
> clojure.lang.Repl
>
> 7. Put the following minimal setup in your .emacs file (adjusting the
> paths as necessary):
>
> (setq load-path (append (list "/Users/bc/lisp/clbuild/source/slime"
> "/Users/bc/lisp/clbuild/source/slime/contrib"
> "/Users/bc/lisp/clojure/clojure-mode"
> "/Users/bc/lisp/clojure/swank-clojure")
> load-path))
>
> (setq swank-clojure-binary "clojure")
>
> (require 'clojure-auto)
> (require 'swank-clojure-autoload)
>
> (defun run-clojure ()
> "Starts clojure in Slime"
> (interactive)
> (slime 'clojure))
>
> (global-set-key [f5] 'run-clojure)
> (global-set-key [(control f11)] 'slime-selector)
>
> (add-hook 'slime-connected-hook 'slime-redirect-inferior-output)
>
> 8. Restart Aquamacs and press F5 - you should get a repl
>
> The above worked for me when I re-installed Clojure (with the latest
> AOT changes) a couple of days ago.
This works for me as well, thanks for the detailed instructions.
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
-~----------~----~----~----~------~----~------~--~---
