On Nov 16, 2008, at 2:40 PM, Peter Wolf <[EMAIL PROTECTED]> wrote:

>
> This is for the other NOOBs...
>
> Apparently to use SLIME with Clojure, you need to install a Common  
> Lisp.

This is not the case.

>
>
> I assumed that SLIME was written in EMACS Lisp, but apparently not.   
> In
> his Blog, Bill did say

You need to install SLIME, but not a Common Lisp.  SLIME includes  
swank implementations for a variety of Common Lisps but not Clojure.   
The swank-clojure project is what allows Clojure to communicate with  
SLIME.

>
>
>    "If you already use a CL implementation with SLIME
> <http://common-lisp.net/project/slime/> and Emacs, then getting setup
> with Clojure is pretty straight-forward."
>
>    http://bc.tech.coop/blog/081023.html
>
> But I didn't realize that meant SLIME was dependent on CL.
>
> I used CMUCL and everything works now.
>
> Thanks
> Peter
>
>
> Peter Wolf wrote:
>> OK, I think I found the problem.  When I start SLIME I get this...
>> See below for my .emacs
>>
>> It looks like SWANK is sending the progn to Clojure which complains.
>> What did I do wrong?
>>
>> Thanks
>> P
>>
>>
>> (progn (load "/usr/share/slime-2008-11-15/swank-loader.lisp" :verbose
>> t) (funcall (read-from-string "swank-loader:init")) (funcall
>> (read-from-string "swank:start-server") "/tmp/slime.27190"
>> :coding-system "iso-latin-1-unix"))
>>
>> Listening for transport dt_socket at address: 8888
>> Clojure
>> user=> java.lang.Exception: Unable to resolve symbol: progn in this
>> context
>> clojure.lang.Compiler$CompilerException: NO_SOURCE_FILE:1: Unable to
>> resolve symbol: progn in this context
>>   at clojure.lang.Compiler.analyze(Compiler.java:3713)
>>   at clojure.lang.Compiler.analyze(Compiler.java:3671)
>>   at clojure.lang.Compiler.access$100(Compiler.java:37)
>>   at clojure.lang.Compiler$InvokeExpr.parse(Compiler.java:2634)
>>   at clojure.lang.Compiler.analyzeSeq(Compiler.java:3860)
>>   at clojure.lang.Compiler.analyze(Compiler.java:3698)
>>   at clojure.lang.Compiler.analyze(Compiler.java:3671)
>>   at clojure.lang.Compiler.access$100(Compiler.java:37)
>>   at clojure.lang.Compiler$BodyExpr$Parser.parse(Compiler.java:3384)
>>   at clojure.lang.Compiler$FnMethod.parse(Compiler.java:3231)
>>   at clojure.lang.Compiler$FnMethod.access$1200(Compiler.java:3142)
>>   at clojure.lang.Compiler$FnExpr.parse(Compiler.java:2766)
>>   at clojure.lang.Compiler.analyzeSeq(Compiler.java:3856)
>>   at clojure.lang.Compiler.analyze(Compiler.java:3698)
>>   at clojure.lang.Compiler.eval(Compiler.java:3889)
>>   at clojure.lang.Repl.main(Repl.java:75)
>> Caused by: java.lang.Exception: Unable to resolve symbol: progn in
>> this context
>>   at clojure.lang.Compiler.resolveIn(Compiler.java:4019)
>>   at clojure.lang.Compiler.resolve(Compiler.java:3972)
>>   at clojure.lang.Compiler.analyzeSymbol(Compiler.java:3955)
>>   at clojure.lang.Compiler.analyze(Compiler.java:3686)
>>   ... 15 more
>> user=>
>>
>>
>> .emacs
>>
>> (add-to-list 'load-path "/usr/share/clojure/clojure-mode")
>> (add-to-list 'load-path "/usr/share/slime-2008-11-15/")  ; your SLIME
>> directory
>>
>> (setq inferior-lisp-program "/usr/share/clojure/clojure") ; your Lisp
>> system
>> (setq swank-clojure-binary "clojure")
>>
>> (require 'clojure-auto)
>> (require 'swank-clojure)
>> (require 'slime)
>> (slime-setup)
>>
>>
>> Peter Wolf wrote:
>>> Hello, I'm feeling dumb...
>>>
>>> I set up SLIME/SWANK/Clojure on my Linux system, but indentation
>>> isn't working.
>>>
>>> The doc says that indentation should "just work"... but nothing
>>> happens.  I tried "indent-region", "indent-sexp" and
>>> "slime-update-indentation"
>>>
>>> What's the trick?
>>>
>>> Thanks
>>> P
>>>
>>>
>>
>>
>
>
> >

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to