Fork me on GitHub
#cider
<
2018-07-25
>
tbaldridge14:07:29

Is this the proper place to ask questions about clj-refactor?

dpsutton14:07:56

@tbaldridge its the best place most likely

👍 8
bozhidar15:07:49

Yeah, I’d say it’s the best place. 🙂

😎 4
dpsutton16:07:06

i've just hit that wrong namespace bug. Seems to be in clojure-cache-ns

dpsutton16:07:14

not sure if that has seen a change recently

dpsutton16:07:40

not sure what's up but (setq clojure-cache-ns nil) has resolved it for me. If you're interested @plexus

bozhidar16:07:38

I figured as much. I just assumed people changed their namespaces using command in clojure-mode, which updates the cache as well. 😉

bozhidar16:07:52

The problem was that not caching the ns was making some ns operations pretty slow for some people and there’s no way to know when to expire it.

achesnais16:07:48

Hey everyone 🙂 It looks like clj-refactor is unavailable through Melpa at the moment – getting a 404 when running package-install or hitting the url directly: https://melpa.org/packages/clj-refactor-20180708.57.tar

achesnais16:07:15

Is anyone experiencing this as well?

bozhidar16:07:30

Seems like some issue on the MELPA side.

bozhidar16:07:50

Probably the build is erring or something.

dpsutton16:07:28

Ah. That makes sense. But I always copy and paste a ns form to start out lol

bozhidar16:07:22

I guess in that case it’s a matter of when clojure-find-ns will kick in first to trigger the caching. 🙂

bozhidar16:07:25

But you make a great point - we should add a basic command to clojure-mode to simple insert a skeleton ns which people can edit.

bozhidar19:07:10

I guess one simple trick would be to expire the cache on file-save, but that’s going to impact negatively the performance you save often while typing.

bozhidar19:07:40

Or this can be expired in cider’s eval commands…

bozhidar19:07:49

Cache invalidation is always hard. 😄