Oh nice. An explicit inclusion of "*[clojure-complete "0.2.2"]*" gets rid
of the complete core stacktrace.

I believe that "*complete/core__init.class*" bug ( ultimately just means
that auto-completion and other facilities aren't available ) comes from how
"*nrepl-ritz-jack-in*" sets up a lein repl (see: this
issue<https://github.com/trptcolin/reply/issues/32>
).

So it sounds like "*nrepl-ritz-jack-in*" ( or rather, the reply from "*lein
repl*" ) "*should check to see if the necessary namespaces are available
immediately upon connecting; if not, load them and proceed.*"


Tim


Tim Washington
Interruptsoftware.ca


"*Today a young man on acid realized that all matter is merely energy
condensed to a slow vibration, that we are all one consciousness
experiencing itself subjectively, there is no such thing as death, life is
only a dream, and we are the imagination of ourselves. Here's Tom with the
Weather.*" -- Bill Hicks



On Sat, Dec 8, 2012 at 6:37 PM, Charles Comstock <dgti...@gmail.com> wrote:

>  I actually just encountered this error, and then intended to post how I
> fixed it as a reported issue and then forgot. So this is my current lein
> profile.clj
>
> {:user {:plugins [[lein-vanity "0.1.0"]
>                   [jonase/eastwood "0.0.2"]
>                   [lein-ritz "0.6.0"]]
>         :dependencies [[ritz/ritz-nrepl-middleware "0.6.0"]
>                        [ritz/ritz-debugger "0.6.0"]
>                        [ritz/ritz-repl-utils "0.6.0"]
>                        [clojure-complete "0.2.2"]]
>         :repl-options {:nrepl-middleware
>                        [ritz.nrepl.middleware.javadoc/wrap-javadoc
>
> ritz.nrepl.middleware.simple-complete/wrap-simple-complete]}}
>  :hooks [ritz.add-sources]}
>
> Note that unlike the docs listed at ritz/nrepl, I also needed to add an
> explicit dependency for clojure-complete 0.2.2. I also needed to use the
> MELPA version of nrepl, nrepl-ritz. I still encounter some sort of issue
> where it appears that the documentation querying functions, find-doc, and
> doc and the like are not being properly brought into the repl namespace,
> which breaks ctrl-d d until I manually bring that into the namespace. I'm
> not quite certain what was causing that problem and have yet to find
> a permanent fix.
>
> The inclusion of clojure-complete should definitely fix the error you are
> getting, but I definitely found setting up the whole ritz setup to be error
> prone.
>
> Charlie
>
> On Wednesday, December 5, 2012 9:09:46 PM UTC-6, frye wrote:
>
>> Ahh yes, `*lein ritz-nrepl*` wasn't working. I got it working by
>> changing the file name to profiles.clj . So Hugo, in the 
>> ritz/nrepl<https://github.com/pallet/ritz/tree/develop/nrepl> page,
>> you'll want to change the instruction text from *A)* to *B)*.
>>
>> *A)* Add this to your ~/.lein/profiles file (requires lein version 2):
>> *B)* Add this to your *~/.lein/profiles.clj* file (requires lein version
>> 2):
>>
>>
>> So with that, I get a little further. And running `*M-x
>> nrepl-ritz-jack-in*` gets me an nrepl shell and server. But the result
>> of the jack-in is an error (see below). I'm not sure if that has to do with
>> ritz, but I'll play around with it:
>>
>> java.io.FileNotFoundException: Could not locate complete/core__init.class
>> or complete/core.clj on classpath:
>>
>>
>>
>>
>>  at clojure.lang.RT.load (RT.java:432)
>>
>>
>>
>>
>>
>>     clojure.lang.RT.load (RT.java:400)
>>
>>
>>
>>
>>
>>     clojure.core$load$fn__4890.**invoke (core.clj:5415)
>>
>>
>>
>>
>>
>>     clojure.core$load.doInvoke (core.clj:5414)
>>
>>
>>
>>
>>
>>     clojure.lang.RestFn.invoke (RestFn.java:408)
>>
>>
>>
>> Thanks very much
>> Tim
>>
>>>
>>>

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

Reply via email to