Clojurians Log v2

anyone use lispy and cider? I’m having trouble with lispy--describe-inline , it throws with the error

Unhandled java.lang.IllegalArgumentException
   Cannot open <nil> as a Reader.

                    io.clj:  288  <http://clojure.java.io/fn|clojure.java.io/fn>
                    io.clj:  288  <http://clojure.java.io/fn|clojure.java.io/fn>
                    io.clj:   69  <http://clojure.java.io/fn/G|clojure.java.io/fn/G>
                    io.clj:  102  <http://clojure.java.io/reader|clojure.java.io/reader>
                    io.clj:   86  <http://clojure.java.io/reader|clojure.java.io/reader>
               RestFn.java:  410  clojure.lang.RestFn/invoke
             analyzer.cljc: 4407  cljs.analyzer$parse_ns$fn__2802/invoke
             analyzer.cljc: 4390  cljs.analyzer$parse_ns/invokeStatic
             analyzer.cljc: 4369  cljs.analyzer$parse_ns/invoke
             analyzer.cljc: 4380  cljs.analyzer$parse_ns/invokeStatic
             analyzer.cljc: 4369  cljs.analyzer$parse_ns/invoke
                 repl.cljc:  604  cljs.repl$load_file$fn__6689/invoke
                 repl.cljc:  601  cljs.repl$load_file/invokeStatic
                 repl.cljc:  593  cljs.repl$load_file/invoke
                 repl.cljc:  761  cljs.repl$fn__6740$self__6742/invoke
                  AFn.java:  165  clojure.lang.AFn/applyToHelper
                  AFn.java:  144  clojure.lang.AFn/applyTo
                  core.clj:  665  clojure.core/apply
                  core.clj:  660  clojure.core/apply
                 repl.cljc:  745  cljs.repl$wrap_self$g__6719/invoke
       piggieback_impl.clj:  287  cider.piggieback/do-eval/fn
                  AFn.java:  152  clojure.lang.AFn/applyToHelper
                  AFn.java:  144  clojure.lang.AFn/applyTo
                  core.clj:  665  clojure.core/apply
                  core.clj: 1973  clojure.core/with-bindings*
                  core.clj: 1973  clojure.core/with-bindings*
               RestFn.java:  425  clojure.lang.RestFn/invoke
       piggieback_impl.clj:  266  cider.piggieback/do-eval
       piggieback_impl.clj:  265  cider.piggieback/do-eval
       piggieback_impl.clj:  323  cider.piggieback/evaluate
       piggieback_impl.clj:  321  cider.piggieback/evaluate
       piggieback_impl.clj:  347  cider.piggieback/load-file
       piggieback_impl.clj:  346  cider.piggieback/load-file
                  Var.java:  384  clojure.lang.Var/invoke
       piggieback_impl.clj:  354  cider.piggieback/wrap-cljs-repl/fn/fn/fn
       piggieback_impl.clj:  201  cider.piggieback/enqueue/fn
                  AFn.java:   22  clojure.lang.AFn/run
               session.clj:  202  nrepl.middleware.session/session-exec/main-loop/fn
               session.clj:  201  nrepl.middleware.session/session-exec/main-loop
                  AFn.java:   22  clojure.lang.AFn/run
               Thread.java:  748  java.lang.Thread/run

been trying to poke around the emacs debugger but don’t really have much experience

try m-x nrepl-toggle-message-logging, try it again, and then open up the messages buffer created for these messages. you can see what its asking the nrepl server to evaluate and see if it makes sense

Anyone else have any issues with cider-doc in a shadow-cljs? It is working fine in my clojure repl and in a different project that uses weasel. It isn’t even working for built-in clojure functions. Toggled messages and just see a ("done" "no-eldoc"). Any ideas?

all it says is => nil. I’ve narrowed it down to being a problem with clj/cljs projects. it works fine in cljs buffers, returns nil in clj buffers, and throws with that error in cljc buffers

I use those two things, but I'm not on the bleeding edge. However I feel like I've seen this exception before... Question for you: Do you "jack in" or do you control your own classpath? I recall that lispy has some funny business with its own dependencies

I think it expects to have pomegranate provided, so that lispy (the clojure part of lispy) can update your classpath dynamically

to add compliment and me.raynes/fs

here

jack in but overridden sometimes. I fixed plain clj projects not having pomegranate on the classpath, but it does not change the mixed clj/cljs project difficulties

https://github.com/abo-abo/lispy/blob/master/lispy-clojure.clj#L30-L44

I control the classpath, rather than using jack-in, and I know I had some snags with lispy

like, if pomegranate isn't available, some of the lispy features break... pretty sure lispy-describe-inline is one that broke for me

hmmm okay. I know cljs has a separate dependency injection. so maybe I will try that.

also rather than messing with the emacs debugger, you could try instrumenting the cljs part

like from that stack trace it seems that it is trying to parse a ns form when it attempts to open nil

could be that there's some subtle problem with one of your ns forms?

if you knew which namespace it's handling in that call to parse_ns on 4407

that might point in the right direction