Hi Andrea, have you checked the doc at
https://github.com/clojure-emacs/cider? It as a bunch of very useful
shortcuts, including the ability to send either eval current buffer,
the current form or the outer most form.
On 9 January 2015 at 12:15, andrea crotti wrote:
> Thank you all for the great
Thank you all for the great suggestions I'll start using some of these
libraries.
I tried now again with cider and found out what I needed to do.
Apparently if I change any file I have to first do a M-x cider-refresh
and then running the tests will reflect the situation.
Can that not be automated
One more suggestion as you mentioned wanting to see more output,
although this may be different from what you were asking--but still
worth knowing about:
https://github.com/pjstadig/humane-test-output
Cheers,
DD
On 2015/01/08 20:30, andrea crotti wrote:
> Hi guys,
>
> I'm starting to use Cloju
I've had good luck with lein prism to cut out any annoying lein startup time.
Mixed in with cider when I want to run one test works nicely for me.
https://github.com/aphyr/prism/
--Ashton
Sent from my iPhone
> On Jan 8, 2015, at 7:32 AM, Malcolm Sparks wrote:
>
> LISP systems work better wh
LISP systems work better when they are continually up-and-running. Take
Emacs for example. Clojure systems aren't much different.
I prefer to think of lein more as a launch tool than a build tool.
I don't think anyone has mentioned it on this thread yet, but lots of
people are using Stuart Sie
Not sure if you know about them but the following are great resources for
finding libraries:
- http://www.clojure-toolbox.com/
- https://github.com/technomancy/leiningen/wiki/Plugins
- http://clojure-libraries.appspot.com/
- https://github.com/trending?l=clojure (to keep up with the cool kid
Ah great that's what I wanted, I'll try later.
Does it give some feedback on what it's compiling and what is going on?
I would use just cider in theory but I had some errors with namespaces
(probably my fault) and more importantly it seemed that it didn't
always recompiled things that were changed
If you want to automate any "lein X" process then lein auto is the thing to
use. However, there are a few runners which will monitor changes and then
run the tests whilst maintaining a lein process so they are really quick.
I personally use https://github.com/jakepearson/quickie, just start "lei
CPU is cheap these days, why not do both?
I tests within CIDER when I want to. But I normally run lein test on
every file change (using a inotify script, but there's probably a nicer
way). This crashes a lot, for instance, when I save a half finished
change, but it also tells me when I have messe
Not sure if you are doing this, you can run the tests in cider itself. This
is much quicker than running "lein test" outside particularly when you are
doing TDD.
I use clojure.test so every deftest method is a function which you can run
to see if the test passes or fails. Or you can run run-tests
The reason lein is initially slow, has to do with Clojures bootstrapping
process, which is slow. People tend to avoid starting clojure programs
repeatedly, and thus do alot of work from the repl, or using leiningen
plugins which keeps running and listens for changes.
Take a look at lein-test-re
Hi guys,
I'm starting to use Clojure a bit more seriously, I knew already Lisp a
bit and Haskell, in plus I've been using Emacs for a long time so
luckily it's not as hard, and it's a lot of fun.
I'm using Emacs + Cider for development and it works wonderfully,
however I have a few problems/quest
12 matches
Mail list logo
