This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-12-22
Channels
- # adventofcode (35)
- # beginners (137)
- # braveandtrue (1)
- # calva (33)
- # cider (40)
- # cljsrn (4)
- # clojure (10)
- # clojure-spec (26)
- # clojure-uk (29)
- # clojurescript (18)
- # core-async (6)
- # cursive (1)
- # emacs (2)
- # figwheel-main (17)
- # fulcro (28)
- # jobs-discuss (4)
- # leiningen (1)
- # lumo (19)
- # off-topic (2)
- # om-next (1)
- # reitit (2)
- # rum (8)
- # spacemacs (19)
- # tools-deps (9)
- # yada (3)
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
@vigilancetech You can safely ignore it. It’s artefact of changes in JDK 9.
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.
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.
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.
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)
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)".
I put [cider/cider-nrepl "0.18.0"] in both :dependencies and :plugins but somehow CIDER feels a lack of it
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.
Well! It still says CIDER requires nrepl..., but on the other hand, I learned to do (cljs-repl) and that seems to work!
CIDER works without cider-nrepl, but in a rather limited way - basically nothing except basic evaluation works this way.
Having said that I always wondered whether things like tests should just default to evaluating clojure.test/run-tests
for instance
> Having said that I always wondered whether things like tests should just default to evaluating clojure.test/run-tests
for instance
@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.
I never found the time for this, though, but it’s relatively simply thing that anyone can do.
Oh yes definitely worth it, should I scan the commits in cider?
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"
@richiardiandrea Sure. I think you have to go back to CIDER 0.6-0.7 if memory serves.
Ok sounds great