@ahmed1hsn - on a fresh install (learning this today) I added the :deps like to my .clojure/deps.edn
and the refresh is working. When I remove that line, it doesn't work (using 1.10 / clj only)
I just turned the auto refresh option off in Chlorine. I didn't like auto refresh in ProtoREPL either
How do you refresh ns'es after change in code?
I evaluate each form as I make changes. I occasionally "load file". If you have a good RDD workflow you just don't need "refresh"
Watch Stu Halloway's talks on RDD. Buy Eric Normand's online course about RDD.
Auto refresh is just a bad idea in my opinion.
Yes, indeed on newer versions of Chlorine auto-refresh is disabled by default
I use clojure.tools.namespace
's refresh because some libraries that I work with don't work with just "load-file" or "simple refresh", they need the whole namespace destroyed and re-constructed (didn't go too far on why).
Kindly elaborate.
Oh I was actually having the same error, searching for it, and found your post above and then set it up as you described and it worked
Which line did you add?
to ~/.clojure/deps.edn
I added
:deps {org.clojure/tools.namespace {:mvn/version "0.3.1"}}
I am launching my repl with clj -A:test:socket
socket is just
:socket {:jvm-opts ["-Dclojure.server.repl={:port,50505,:accept,clojure.core.server/repl}"]}
Which version of Clojure and Chlorine are you using?
Clojure 1.10.1, Chlorine 0.1.10
I was using same versions but I'm getting error on first refresh. Subsequent refreshes work fine.
Just a fast update, a new update on Chlorine is almost ready. The only thing that I'm having some issue is that I enabled a new configuration "enable experimental features" that is disabled by default, but sometimes this configuration is not appearing on the plug-in tab, and Atom is not honoring the default...
Just published a new version. Mostly bug fixes, but also I'm getting rid of some internal Atom APIs, changed default configurations to more sensible ones, fixed some issues with ClojureScript autocomplete, and added a config to be able to use experimental features. Also, I'm keeping a very complete changelog, so details about experimental features should be there too 🙂