This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-07-25
Channels
- # beginners (26)
- # boot (1)
- # cider (21)
- # cljdoc (26)
- # cljs-dev (7)
- # clojure (99)
- # clojure-gamedev (6)
- # clojure-italy (5)
- # clojure-nl (4)
- # clojure-russia (1)
- # clojure-spec (5)
- # clojure-uk (59)
- # clojurescript (49)
- # clojutre (6)
- # component (13)
- # core-async (2)
- # cursive (30)
- # data-science (2)
- # datomic (29)
- # emacs (9)
- # fulcro (100)
- # hyperfiddle (1)
- # jobs (2)
- # luminus (4)
- # lumo (23)
- # off-topic (22)
- # other-languages (37)
- # parinfer (1)
- # re-frame (2)
- # reagent (5)
- # reitit (12)
- # ring (12)
- # rum (3)
- # shadow-cljs (168)
- # slack-help (1)
- # spacemacs (7)
- # specter (2)
- # tools-deps (8)
- # vim (11)
- # yada (3)
Is this the proper place to ask questions about clj-refactor?
not sure what's up but (setq clojure-cache-ns nil)
has resolved it for me. If you're interested @plexus
I figured as much. I just assumed people changed their namespaces using command in clojure-mode
, which updates the cache as well. 😉
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.
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
I guess in that case it’s a matter of when clojure-find-ns
will kick in first to trigger the caching. 🙂
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.