On Sep 28, 2014, at 9:57 AM, Steve Ford <fordsfo...@gmail.com> wrote: > Any suggestions besides killing and restarting "lein midje :autotest" from > time to time? (To be avoided given the long delay starting it.)
You can use Stuart Sierra's workflow: description: http://thinkrelevance.com/blog/2013/06/04/clojure-workflow-reloaded tooling: https://github.com/stuartsierra/reloaded I myself haven't bothered switching, because I push frequently and the continuous integration server will catch those problems. (Or, when I'm pushing less frequently, I'll occasionally toss off a plain `lein midje` in a shell buffer somewhere.) Note: Rather than `lein midje :autotest`, you can also run autotest in the repl. I prefer it: 546 $ lein repl nREPL server started on port 51091 on host 127.0.0.1 user=> (use 'midje.repl) Run `(doc midje)` for Midje usage. Run `(doc midje-repl)` for descriptions of Midje repl functions. nil user=> (autotest) ====================================================================== Loading (midje.data.fact midje.util.exceptions ... = Namespace implementation.line-numbers.fim-check-failures ... 0 failures, 0 errors. >>> Midje summary: All checks (736) succeeded. [Completed at 15:02:22] true user=> -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
