Re: :reload does not always work correctly in leiningen

2015-03-03 Thread Akiva Schoen
I normally use a set utility functions to reload individual namespaces so I don't lose state. This almost always suffices for day-to-day work. But, if the REPL is still acting shady, then I'll use refresh. Anything is better than having to wait out a REPL reboot. On Sat, Feb 28, 2015 at 10:43 AM J

Re: :reload does not always work correctly in leiningen

2015-02-28 Thread Cecil Westerhof
2015-02-28 17:26 GMT+01:00 Sam Raker : > "does not always work correctly " in what context? > ​One time when I did the reload my forms got an empty area around them. After an exit and a new start everything was OK again. I use it since today, so I do not know if it is a gremlin or a real problem.

Re: :reload does not always work correctly in leiningen

2015-02-28 Thread James Reeves
The :reload directive re-evaluated the namespace, but does not remove any existing definitions, or reload any dependent namespaces. This may be the cause of your "strange results". The tools.namespace library contains a "refresh" function that will clea

Re: :reload does not always work correctly in leiningen

2015-02-28 Thread Sam Raker
"does not always work correctly " in what context? In the REPL, `(require '[my.ns :as mine] :reload-all)` should work. `defonce` and `defmulti` might also be causing confusion. You could also look into `clojure.tools.namespace.repl` (https://github.com/clojure/tools.namespace#reloading-code-usa

:reload does not always work correctly in leiningen

2015-02-28 Thread Cecil Westerhof
I discovered: (require 'project.core :reload) Very handy indeed and a big time saver. But it does not always work correctly. At a certain moment I got strange results. An exit and a new 'lein repl' solved the problems. -- Cecil Westerhof -- You received this message because you are subscri