This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-06-18
Channels
- # aws (12)
- # beginners (489)
- # calva (32)
- # cider (117)
- # clj-kondo (4)
- # cljdoc (9)
- # cljs-dev (3)
- # clojure (56)
- # clojure-brasil (1)
- # clojure-europe (10)
- # clojure-italy (44)
- # clojure-nl (9)
- # clojure-russia (1)
- # clojure-sweden (6)
- # clojure-uk (64)
- # clojurescript (6)
- # cursive (6)
- # datascript (4)
- # datomic (6)
- # emacs (3)
- # fulcro (15)
- # graalvm (11)
- # jackdaw (7)
- # jobs (8)
- # jobs-discuss (29)
- # jvm (2)
- # leiningen (5)
- # luminus (10)
- # off-topic (23)
- # pathom (21)
- # planck (11)
- # quil (6)
- # re-frame (11)
- # reagent (17)
- # reitit (8)
- # rewrite-clj (6)
- # shadow-cljs (78)
- # slack-help (2)
- # spacemacs (7)
- # specter (4)
- # sql (60)
- # tools-deps (7)
- # xtdb (11)
I think repl window is limited, so my workflow is using external terminal to run nrepl, and connect repl window to nrepl instead of jack-in
@minhnhat10bk: You can also jack-in and then connect an internal or external terminal with something like lein repl :connect
. That way you won't need to keep track of the Calva dependencies.
@pez I found that Ctrl+Alt+C, Enter
works well. In my scenario, I had the user
ns in dev resources use another ns dev-data
in dev resources which wasn't reloaded when I did (use 'user :reload)
in the REPL window but doing Ctrl+Alt+C, Enter
in dev_data.clj
does reload that ns
Well... just tried to reproduce this... (use 'user :reload)
seems to work just fine now. No idea what was going on...
:man-shrugging:
@pez, I'm getting a bit of a regression on 2.0.14. I'm not sure I can describe the symptoms adequatly. The web-app part of it is suddenly unable to find resources that are plainly there. When I revert to 2.0.13, the problem disappears.
I can dig in and maybe even bisect it later. Right now, a bit in the fray, and just wanted to alert/jog because .14 for me is being toxic
There is a risk it is the bundling. But I need much more detailed and exact descriptions of what is going wrong.
Can you try this one, @hoppy? I am hoping it will not fix the problem, but also realising that it might…
I really would like to be able to keep bundling the extension. But I can’t see what else could be causing it to get toxic.