Fork me on GitHub

I suspect vim's "insert" is given higher priority then cider's "in" (as in "step in", with the debugger context). How do i verify that and whats the best way to change it?


It seems many of us just work around the issue using C-z to switch to Emacs editing mode, then the same to switch back to evil when finished with the cider debugger. Would be good to get this fixed for evil though.

👍 4
🙂 4

Thanks for the info.


i get the same behavior you got. cool cool


First time developing Clojure in a while so my tools may be out of date. I'm going by the Practicalli guide, and I started the project with Sean Corfield's clj-new. If I use , t a I get a message, "No assertions (or no tests were run). Did you forget to use 'is' in your tests?" But if I view the boilerplate test and run , t t I get a nice pretty output window. :thinking_face:


@mathpunk Also try , t n to run all the tests in the current namespace, it should load the tests into the REPL too, so you dont always have to evaluate them. (adding this to the book quickly) To make certain the tests run, they should be evaluated (just like functions in the src code), so , e f for individual fuctions or , e b for the whole namespace (buffer). If you change the name of a deftest, use , e u to unevaluate that test first or it will keep running until you restart the repl.


Also if you have test dependencies under an alias, create the M-x add-dir-local-variable and add cider-clojure-clj-global-options with your alias, for example:`"-A:test"`


If it doesn't work, restart spacemacs after creating that file.


When using the CIDER test runner, you will need to add the test path somewhere in the deps.edn of the project too