This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-10-25
Channels
- # 100-days-of-code (6)
- # announcements (4)
- # aws (2)
- # beginners (151)
- # boot (1)
- # calva (1)
- # cider (19)
- # clara (47)
- # cljdoc (9)
- # cljs-dev (25)
- # clojars (18)
- # clojure (151)
- # clojure-canada (1)
- # clojure-conj (1)
- # clojure-dev (17)
- # clojure-italy (42)
- # clojure-nl (34)
- # clojure-spec (67)
- # clojure-uk (125)
- # clojurescript (163)
- # core-async (106)
- # cursive (19)
- # data-science (11)
- # datomic (9)
- # duct (2)
- # figwheel (1)
- # figwheel-main (6)
- # fulcro (97)
- # graphql (9)
- # instaparse (4)
- # jobs (6)
- # jobs-discuss (21)
- # leiningen (62)
- # mount (23)
- # off-topic (16)
- # re-frame (15)
- # reagent (16)
- # reitit (5)
- # remote-jobs (1)
- # ring-swagger (9)
- # shadow-cljs (176)
- # tools-deps (102)
- # unrepl (3)
I thought you said you just started a clj connected and upgraded it manually yourself.
I wonder if it just me, but lately CIDER became much more aggressive about caching stuff. E.g., when I switch connections for the buffer with Sesman, I have to revert-buffer
before the effect is seen. Or if I change the name of the Clojure file and the namespace name, CIDER seems to remember the previous namespace until I revert the buffer. Is this a known issue, or should I dig deeper into my setup?
Also, why did CIDER recently switch to boot cider.tasks/nrepl-server
command instead of boot repl
? The former does quite many things wrong, I'd consider that a breaking change.
i think only one contributor to CIDER uses boot with any frequency. I'm sure PRs would be quite welcome
@alexyakushev because the cider.tasks makes it possible to inject middleware.
My fault 😄 I wrote that and it just wraps nRepl..maybe I left a bug behind or something?
what's the advantage or disadvantage of using shadow-cljs' built in nrepl vs cider-nrepl (when using cider)?
@dominicm This worked with boot repl
as well, but the new task helped us circumvent the old nREPL shipped with boot prior to the most recent version. Plus, when released this the new version wasn’t even out if I recall correctly.
> Also, why did CIDER recently switch to boot cider.tasks/nrepl-server
command instead of boot repl
? The former does quite many things wrong, I’d consider that a breaking change.
@alexyakushev What are the problems you’ve spotted with this task?
> I wonder if it just me, but lately CIDER became much more aggressive about caching stuff. E.g., when I switch connections for the buffer with Sesman, I have to revert-buffer
before the effect is seen. Or if I change the name of the Clojure file and the namespace name, CIDER seems to remember the previous namespace until I revert the buffer. Is this a known issue, or should I dig deeper into my setup?
Wasn’t this a bug in clojure-mode
that we fixed since? I’ve added some ill-conceived ns lookup caching to clojure-mode
at some point, but I’ve disabled it afterwards, before someone can find time to revisit it. clojure-find-ns
was a bottleneck for certain ops, by my caching strategy caused more problems than it solved.