Clojure Development Workflow with Spacemacs and CIDER

This is a follow-up to my previous post What’s the Best Clojure IDE? I’ll show you my usual Clojure development workflow using Spacemacs+CIDER as primary tools.

I’ve already described my tour through the various Clojure IDEs/editors and why I’ve chosen the Spacemacs. If you haven’t read the previous post, you may want to go back and read at least the Spacemacs to the rescue part.

In this post, I’ll try to dig deeper and show you the complete development workflow. I’ve chosen video screencast as a primary format for this because I think it’s more useful to see everything in action.

We’ll create a simple clojure-repl project containing the jmethods function for listing all public methods of java classes.

You can find the video in the Curious Programmer YouTube channel.

Below is a brief summary of topics/tips presented in the screencast.


  • Generate new leiningen project: lein new clojure-repl
  • Open Spacemacs
  • Create new layout: SPC l 2; enter layout name: clojure-repl
  • Open clojure-repl/project.clj by pressing SPC f f and looking up the file on a file system
  • Open Neotree buffer via SPC p t to explore project structure
    • You can navigate in this buffer via standard vim key bindings: j, k, l, h. You can also press ? to open the help
  • Clean the initial project skeleton and commit them via magit: SPC g s
    • Expand/collapse the changes by pressing TAB
    • Stage the changes for commit by pressing s
    • Commit the staged changes by c c
  • Create java.clj file in the Neotree buffer by pressing c (“create”) and entering the name of the file.
  • Run cider-jack-in by , '
  • Switch between REPL and java.clj buffer using C-c C-z
  • Evaluate the java.clj buffer via , e b
  • Evaluate the function at a point by , e f
  • Send results from java.clj buffer to the REPL using , s e while keeping cursor right after the form you want to evaluate
  • Use clojure.core/bean function to examine the properties of java class
  • Reformat a buffer with , = to make sure that your code is compliant with Clojure style guide
  • Use SPC k s for “forward slurp”
  • Use cljr-add-missing-libspec , r a m to add a require unknown symbols (e.g. clojure.string/join) automatically
  • Show documentation popup with , h h
  • Navigate to source code by , g g


Additional tips mentioned at the end of the video:

  • Describe key bindings via SPC ?
  • Start with M-x and type in the “cider-” and/or use menu bar (F10) to search for CIDER commands and explore CIDER capabilities
  • Add new dependencies to project.clj and hot-load them into the REPL via , r a p
  • cider-inspect-last-result
    • press ENTER to deep dive
    • press C-z to switch into the Emacs mode and then l to go up
  • Use SPC / for a quick search within the project
    • You can also use C-c C-e to enter the edit mode and replace the text
  • Type * for a quick search/highlight of a symbol under the cursor
  • Display online java doc for Java class with , h j
  • Add Clojure sources to the project.clj/profiles.clj to be able to navigate to clojure.core java classes, e.g. clojure.lang.PersistentVector
  • Not covered in video
    • cider-browse-ns , h n to list all the functions in given namespace together with a documentation preview
    • cider-refresh  , s x to test everything in a fresh environment
    • CIDER debugger – debug function at the point: , d b


What’s the Best Clojure IDE?

In this article, I’ll evaluate the Emacs, Cursive, and Spacemacs, and explain why I ended up with Spacemacs for most of the projects I’m currently working on.

It’s been a while since I started coding in Clojure, but the “IDE dilemma” was there from the beginning. Although some people might think that it’s a waste of time and you can just pick any editor you want, I disagree. There’s definitely a big difference in terms of productivity if you can use the best tool for the job.

My Tour Through the Clojure IDEs’ Country

Emacs LIVE

In the beginning, I did a quick research and found out that many people in Clojure community use Emacs.

I had never really used Emacs. However, I found one particular Emacs incarnation, Emacs LIVE, specially crafted for beginners. Of course, there still was a big learning curve for me. I spent countless hours getting used to Emacs editing style, shortcuts, and quirks of Emacs LIVE.

On the one hand, it was packed up with useful plugins. On the other hand, its config was bloated, and it was slow to start.

Eventually, I was not able to distinguish if my problems (such as broken keyboard shortcuts for slurp and barf) were related to the specifics of Emacs LIVE or if they were some general issues with Emacs or my Mac OS X configuration.


In the meantime, I also played with Cursive.

As a long-time IntelliJ IDEA user, I happened to be familiar with the environment. I really love the features like Full-text search, Project tree window, Symbol navigation, Refactoring, Git integration, Live Templates, Database Plugin, and more.

However, for smaller projects, Cursive feels too heavy-weight:

  • Its start up time is slower.
  • ClojureScript and Figwheel integrations aren’t very good (yet).
  • Regarding plain old text editing, Vim and Emacs provide a better experience.

I love Cursive’s features and need them to be productive. I do think that Colin Fleming is doing a great job. But I also need something more lightweight which doesn’t consume a lot of resources.

Emacs – From the Scratch

Being unable to fix some issues in Emacs LIVE, I finally stepped back and started with plain Emacs, adding only plugins I needed. Step by step, I added projectile, project-tree-explorer (later replaced by NeoTree since project-tree-explorer was painfully slow for large projects), auto-complete, company-mode, and more.

You can find my old Emacs configuration on GitHub. One interesting piece is the configuration for Figwheel.

;; Cider figwheel integration
(require 'cider)
;; more elaborate cider-cljs-lein-repl than in official documentation
;; this tries to match the project type
;; copied from
(setq cider-cljs-lein-repl
 (and (resolve 'user/run) (resolve 'user/browser-repl)) ;; Chestnut projects
 (eval '(do (user/run)
 (require 'figwheel-sidecar.repl-api)
 (resolve 'figwheel-sidecar.repl-api/start-figwheel!)
 (catch Throwable _))
 (eval '(do (figwheel-sidecar.repl-api/start-figwheel!)
 (require 'cemerick.piggieback)
 (resolve 'cemerick.piggieback/cljs-repl)
 (catch Throwable _))
 (eval '(cemerick.piggieback/cljs-repl (cljs.repl.rhino/repl-env)))
 (throw (ex-info \"Failed to initialize CLJS repl. Add com.cemerick/piggieback and optionally figwheel-sidecar to your project.\" {})))")

Previously, I struggled a lot with a proper setup for ClojureScript projects including browser-connected REPL, Figwheel and CIDER integration.
That Lambda Island episode finally got me some setup that worked.

Again, it took me non-trivial amount of time to configure my Emacs and learn new shortcuts. Yet I still had some issues with code formatting and usability. I was never quite happy with using Emacs for large projects, especially for the ones I wasn’t familiar with. Therefore, I ended up using Cursive for every larger code base I encountered.


Spacemacs to the Rescue

Recently, I visited The second Brno Clojure meetup and had a great discussion with Karel Miarka about many topics, including Clojure editors. Instead of using plain Emacs, he recommended the Spacemacs distribution.

Getting Started with Spacemacs

I found following resources to be perfect for getting started with Spacemacs:

  1. Spacemacs documentation
    1. Quickstart
    2. Full Documentation
  2. Clojure development with Spacemacs from

The Introductory video is fascinating and made me curious. If that’s how the Spacemacs works, maybe I can use Emacs again without frustration even for large real-world projects.

The downside: I had to learn a little bit different workflow and shortcuts once again.
The upside: easy and almost automatic configuration and good pre-configured plugins.

My Spacemacs Configuration

Since Spacemacs configuration is almost automatic, I did a very little custom configuration:

  • I uncommented following dotspacemacs-configuration-layers in .spacemacs file (use shortcut SPC f e d for quick edit of .spacemacs file and SPC f e R for quick reload)
    • helm
    • auto-completion
      • By using this layer, you can automatically expand code snippets like defn via M-/ (yas-expand) to simulate Cursive’s Live Templates
    • better-defaults
      • few enhancements of standard commands like C-a, C-e, C-w, C-y, M-q
    • git
      • magit provides an incredible Git experience inside the editor.
      • Start with magit-status: SPC g s
      • Unlike many developers who use the Git only from command line, I believe there’s value in having strong Git integration within IDE. I used to use IniteliJ “Commit dialog” a lot and now I have a similar (and maybe even better) experience with magit.
  • I activated hybrid-mode instead of default-mode: dotspacemacs-editing-style 'hybrid
    • This means that you can use emacs shortcuts like C-a and C-e when you are in vim editing mode – very useful!
  • I turned on line numbers by default: dotspacemacs-line-numbers t
    • I can always turn them off via SPC t n


There’s a nice shortcut , (comma) which serves as a prefix for all Cider commands. For instance , t a will run all unit tests for current namespace. Alternatively, you can use SPC m prefix: SPC m t a

Other than that, Cider integration is just seamless and very similar to the ordinary Emacs.


Layouts are one of the more useful features that I didn’t use from the very beginning.

Basically, the layout is a set of related buffers. Something you could call a project in more traditional IDEs. The layout will help you to organize your buffers.

There is always at least one layout called Default. To create a new layout, press SPC l and then 2. Type the name of the new layout and you’re all set up. You can start creating new buffers. When you press SPC l b, you’ll see only buffers assigned to the current layout (except the Default one which contains all buffers).

Final Thoughts

Nowadays, Spacemacs is my tool of choice for all Clojure projects – both small samples and large code bases with thousands lines of code. I think it’s a great development environment with tons of useful features like Cider REPL, Git integration, Neotree explorer, layouts, and more. I found it more approachable for non-expert Emacs users than vanilla Emacs.

If I work on some project with lots of Java/JavaScript code in the future, I will probably switch back to Cursive.

How About the Atom + Proto REPL?

A Few days ago, I watched the Clojure/conj talk Proto REPL, a New Clojure Development and Visualization Tool by Jason Gilman and it completely blew my mind. The debugging and visualization capabilities of Proto REPL are brilliant.

However, when I tried Atom with Proto REPL it just didn’t feel right to me. To be honest, I didn’t spend much time with it (I have other things to do besides testing all possible Clojure editors). For now, I feel more productive and organized with Spacemacs, so I’ll stick with it. I’m pretty sure I’ll revisit Atom + Proto REPL at some point in the future.