Fork me on GitHub
#cider
<
2018-12-22
>
vigilancetech03:12:57

anyone know why I'm getting this (with shadow-cljs)

WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by cider.inlined_deps.orchard.v0v3v4_20181106v231743_
1.dynapath.v0v2v5.dynapath.defaults$eval30899$fn__30900 to method java.net.URLClassLoade
r.addURL(java.net.URL)
WARNING: Please consider reporting this to the maintainers of cider.inlined_deps.orchard
.v0v3v4_20181106v231743_1.dynapath.v0v2v5.dynapath.defaults$eval30899$fn__30900

bozhidar07:12:50

@vigilancetech You can safely ignore it. It’s artefact of changes in JDK 9.

practicalli16:12:32

can someone confirm that M-x clojure-cheatsheet is now replaced with M-x cider-cheatsheet? It seems that clojure-cheatsheet doesnt do anything (at least in my setup) but cider-cheatsheet works just fine.

Chase16:12:37

clojure-cheatsheet pulls up for me in a browser if that's what you are looking for. It seems to want it to be clojure-view-cheatsheet. When I use cider-cheatsheet it seems to let me dial down to a specific variable. I haven't used these before so not sure if that helps.

bozhidar17:12:17

@jr0cket Yeah, I can confirm this.

bozhidar17:12:44

The only real difference is that clojure-cheatsheet had a hardcoded dependency on helm and cider-cheatsheet is presentation-agnostic, meaning you can easily render the data with every front-end you can imagine.

practicalli17:12:47

clojure-cheatsheet seems to be broken in Spacemacs, gives the error helm-M-x: Cannot open load file: No such file or directory, cider-interaction. So I was going to update the clojure layer to use cider-cheatsheet instead (which works nicely)

phill18:12:46

I did cider-connect-cljs (figwheel) and got this message "CIDER requires cider-nrepl..." and also the mode line says (pending-cljs) even though figwheel already displayed its dev:cljs.user=> prompt after node.js connected to it. Was trying to follow the notes at https://github.com/lambdaisland/npmdemo and chose the figwheel option because of that lambdaisland phrased as "the possibility to connect with nREPL (e.g. with Emacs/CIDER)".

phill18:12:54

I put [cider/cider-nrepl "0.18.0"] in both :dependencies and :plugins but somehow CIDER feels a lack of it

bozhidar18:12:45

Are you using figwheel-sidecar?

phill18:12:58

Yes it is among the :dependencies

phill18:12:51

Also cider/piggieback 0.3.9

bozhidar18:12:18

How did you start the repl exactly?

phill18:12:25

lein figwheel

phill18:12:56

The project clj says :figwheel { :nrepl-port 3451} and I connected CIDER to that port

bozhidar18:12:06

Got it. That explains it.

phill18:12:12

The connection apparently succeeded, (clojure-version) says 1.9.0

bozhidar18:12:57

I think the problem is that figwheel doesn’t add cider-nrepl automatically to the server it starts, so it will probably be best to start the server yourself and then run figwheel manually from the REPL.

bozhidar18:12:01

E.g. something like this

bozhidar18:12:34

Probably using cider-jack-in-cljs will work better for you as well.

phill18:12:49

Well! It still says CIDER requires nrepl..., but on the other hand, I learned to do (cljs-repl) and that seems to work!

phill18:12:15

oh - I should try cider-jack-in-cljs.

bozhidar18:12:56

CIDER works without cider-nrepl, but in a rather limited way - basically nothing except basic evaluation works this way.

richiardiandrea18:12:06

Having said that I always wondered whether things like tests should just default to evaluating clojure.test/run-tests for instance

phill18:12:12

Wow this is pretty nifty

bozhidar18:12:27

> Having said that I always wondered whether things like tests should just default to evaluating clojure.test/run-tests for instance

bozhidar18:12:06

@richiardiandrea It used to be like this. In hindsight I regret removing the fallbacks and I wanted to add them back to for most basic ops - source lookup, doc lookup, etc.

bozhidar18:12:26

I never found the time for this, though, but it’s relatively simply thing that anyone can do.

bozhidar18:12:24

I guess that’d be extra useful on the ClojureScript front.

richiardiandrea18:12:58

Oh yes definitely worth it, should I scan the commits in cider?

phill18:12:53

Goodness gracious, cider-jack-in-clj&cljs is an experience. It totally blows away the silly old advice, "do one thing and do it well"

phill18:12:32

I think I will try Clojure 1.10

bozhidar19:12:14

@phill Happy to hear this!

bozhidar19:12:24

> Oh yes definitely worth it, should I scan the commits in cider?

bozhidar19:12:49

@richiardiandrea Sure. I think you have to go back to CIDER 0.6-0.7 if memory serves.