David Pollak <[email protected]> writes:
Hi David,
> * Is there a faster cycle than to change code, change tests and type
> "lein test" to see the results?
Obviously, you can run the tests from the already running REPL. FWIW,
when I change something in using Emacs/nrepl.el/clojure-mode in a
namespace, I do
C-c C-k ;; recompile the namespace
C-c C-t ;; switch to the corresponding test namespace (I think the
;; original key binding is `C-c t'.)
;; maybe adapt the tests if needed, and if so
C-c C-k ;; recompile the test namespace
C-c M-n ;; switch the REPL to the test namespace
;; switch to the *nrepl* buffer
(run-all-tests)
The latter can also be called with a key binding and nicer output
highlighting using clojure-test-mode, but I haven't given it a try, yet.
> * Is there a way to keep everything in a hot JVM (I've done a little
> research on Nailgun... but it seems to be out of vogue) so there's no
> JVM start-up penalty?
There's drip (https://github.com/flatland/drip) which will always keep a
fresh JVM in the background.
> * Is there a reason for the huge disparity between my MacBook Pro and
> my desktop box?
Yes, most definitively. Unfortunately, I don't know it. ;-)
Bye,
Tassilo
--
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to [email protected]
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
[email protected]
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
