Fork me on GitHub
#cider
<
2018-10-25
>
bozhidar06:10:50

@pri Yeah, that’s true. But I think we addressed most of them on master.

bozhidar06:10:02

Btw, why do you have two connection in the same session in the first place?

bozhidar06:10:18

I thought you said you just started a clj connected and upgraded it manually yourself.

alexyakushev10:10:00

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?

alexyakushev14:10:48

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.

dpsutton14:10:59

i think only one contributor to CIDER uses boot with any frequency. I'm sure PRs would be quite welcome

dominicm14:10:37

@alexyakushev because the cider.tasks makes it possible to inject middleware.

dominicm14:10:54

I wasn't aware of anything it did wrong since using it, what does it do wrong?

richiardiandrea14:10:05

My fault 😄 I wrote that and it just wraps nRepl..maybe I left a bug behind or something?

vigilancetech19:10:42

what's the advantage or disadvantage of using shadow-cljs' built in nrepl vs cider-nrepl (when using cider)?

dpsutton19:10:51

cider-nrepl is middleware for nrepl which shadow also uses.

👍 1
bozhidar20:10:43

@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.

bozhidar20:10:55

> 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.

bozhidar20:10:17

@alexyakushev What are the problems you’ve spotted with this task?

bozhidar20:10:46

> 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?

bozhidar20:10:21

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.

bozhidar20:10:10

I’m pretty sure fixing this would be simple, but I’m juggling waaay too many things right now. For the time being I’ve decided to focus my efforts on nREPL and put most of my other work in background mode.

pre21:10:08

@bozhidar I’m using 102418 snapshot and cider-jack-in-clj-&-cljs doesn’t connect clj source to the clj repl started. As I mentioned in my comments, I had to “connect as a sibling’ manually to enable clojure form evaluation.