## Why this combo?

I’ve been using jEdit for some time as my general purpose editor and “IDE” (especially for Ruby on Windows) so it was natural to start there for my first forays into Clojure, dropping out to e.g. Leiningen for a REPL.

But debugging Clojure is more of a challenge than, say, Ruby because the stack trace is a Java one and its not as easy to associate the Clojure source file and line number with entries in the stack trace.

Also, I’ve found introducing print statements (e.g. println) into functional code make its look far noisier than OO code to the point where I find it obfuscates what the code is doing. This is partly a matter of taste but to me functional code looks far more elegant and transitive when compared to imperative and anything that interrupts the flow is a distraction.

After reading around the Clojure community for a better solution, the combination of Emacs, SLIME and Swank (supported by Leiningen) appeared to offer a far richer development and debugging environment so I thought I’d give it a go.

In the past though getting all these components to play nice has been frustrating for some. Phil Hagelberg has contributed a huge amount to making the setup easy for newbies. So this post, and the recipe in it, is really a paean to Phil (and numerous others who have made contributions!) who made this process straightforward for me.

## What is SLIME and Swank?

Slime is inevitably an acronym: the Superior Lisp Interaction Mode for Emacs

The manual say:

SLIME is constructed from two parts: a user-interface written in Emacs Lisp, and a supporting server program written in Common Lisp. The two sides are connected together with a socket and communicate using an RPC-like protocol.

Swank is the “supporting server”.

## So why would you bother?

What does this mean in practice? Its the ability to edit Clojure code in Emacs and ask SLIME to execute the code in the Swank server giving immediate feedback - truly interactive development.

## How I tested the recipe below

This post encapsulates knowledge picked up over a period of time but I have tested each of the steps in a VirtualBox (4.1.16) guest running Ubuntu Precise Pangolin 12.04 with fairly recent updates, and the usual toolset (git, wget, etc). Nevertheless mistakes may have crept in so please let me know and I’ll correct and refresh.

## Install Emacs 24

I covered installed Emacs 24 from source in a previous post

Using Emacs 24 seems to forestall problems others have had.

## Install Leiningen 2 preview.

See here for full details but briefly:

Asking lein what version it is will cause it to bootstrap itself and download whatever dependencies it needs.

emacs delete tabs

On my machine the last line output said:

Leiningen 2.0.0-preview6 on Java 1.7.0_03 OpenJDK 64-Bit Server VM

## Install Phil’s Emacs starter kit

Full details again from Phil’s github page.

Following the advice given, my ~/.emacs.d/init.el looks like this:

## Making SLIME/Swank integration available to all my projects

I wanted Swank integration to all my projects rather than project by project. So my ./.lein/profiles.clj looks like this:

## A simple test

To test and see the Emacs integration with SLIME/Swank, a new, test project was created:

I’m using Clojure 1.4 so I edited swanktest’s initial project.clj to say so:

Any changes needed to be applied and dependencies resolved:

Next, Emacs was satrted and swanktest’s src/swanktest/core.clj edited by e.g. C-x C-f and navigating to core.clj

From within Emacs a Swank server was started using M-x clojure-jack-in and after a while an image similar to the following appeared:

###

BTW A list of SLIME commands can be found on Phil’s swank-clojure page.

## What’s Next?

Learning how to make the most of the integration - some experiences / examples likely to follow in later post.