Setting up a working Common Lisp environment for the aspiring Lisp newbie

Question

I\'ve been a UNIX sysadmin for a long time, and aside from automating tasks with shell scripting, some light PHP work, and a few simple C programs, I\'ve never done much in the

Answer 1

Did you try Lispbox?

Answer 2

Lispbox & SLIME are fine answers, but if you want something even simpler, just to play with, you might consider the free version of LispWorks Personal or Allegro CL Free Edition. I have not used either on linux myself, but they both appear to come with GUIs. There will be heap size or other limitations (since the full versions are not free), but they may be easier to dive into.

Answer 3

Well, a good place to start would be the executing lisp section of the info pages.

In general, when you work with an interpreted language in Emacs, you edit the source files, and interact with an inferior process (a new process spawned by Emacs, in this case a lisp process). You can evaluate an sexp (balanced expression), region, or the entire buffer with simple keystrokes. Those commands send the code to the lisp process and evaluate it.

This usage model works for shells, Tcl, lisp, anything with an interpreter...

The wiki has a lot of good information.

Answer 4

Let's assume you have emacs running and have checked out SLIME from CVS and installed it. This should be easy with any Linux distro; apt-get install emacs slime does it for me. (You should also install SBCL, the best Common Lisp implementation.)

SLIME out of the box doesn't do much anymore, so it needs configuration. Configuring emacs is done in your ~/.emacs file. Visit that file (C-x C-f ~/.emacs). I have something like this, which loads a variety of goodies:

(eval-after-load "slime"
  '(progn
     (setq slime-lisp-implementations
           '((sbcl ("/usr/bin/sbcl"))
             (ecl ("/usr/bin/ecl"))
             (clisp ("/usr/bin/clisp"))))
     (slime-setup '(
                    slime-asdf
                    slime-autodoc
                    slime-editing-commands
                    slime-fancy-inspector
                    slime-fontifying-fu
                    slime-fuzzy
                    slime-indentation
                    slime-mdot-fu
                    slime-package-fu
                    slime-references
                    slime-repl
                    slime-sbcl-exts
                    slime-scratch
                    slime-xref-browser
                    ))
     (slime-autodoc-mode)
     (setq slime-complete-symbol*-fancy t)
     (setq slime-complete-symbol-function
  'slime-fuzzy-complete-symbol)))

(require 'slime)

If you don't have SLIME installed in your "site directory", you'll also want to add this before those lines:

(add-to-list 'load-path "~/elisp/slime/")
(add-to-list 'load-path "~/elisp/slime/contrib")

(Change the these paths to the correct location, of course.)

The key part is the slime-setup, this loads a variety of optional modules, including the REPL. (I also consider the fancy indentation, and autodoc essential.)

Anyway, you can load this into your running emacs with M-x eval-buffer, or by putting the point inside each sexp and pressing C-M-x. (You can also point to the end of the sexp and press C-x C-e. There are a variety of ways to evaluate Emacs Lisp in Emacs, but that is not really relevant to learning CL.)

At this point, you should be able to type M-x slime and be taken to your REPL. Before that happens, your lisp will be loaded, SLIME will tell it to compile Swank (the CL side of SLIME), and you will see that happen. This only happens once, though, next time SLIME will start up faster.

At the REPL, you can type Common Lisp commands and see the result of their evaluation. Pressing TAB to complete something will bring up a window of possible completions; this is smart completion, so typing something like "d-b" will bring up a list containing "destructuring-bind". Very helpful. M-/ will also complete symbols that you have already typed somewhere inside Emacs; another great time saver. (This works everywhere in Emacs, BTW, and is called "dynamic abbreviation expansion".)

Earlier you said the REPL was boring, so let's open a real file. Press C-x C-f test.lisp. Not surprisingly, this will open up a buffer editing test.lisp, which will be created when you first save the file (C-x C-s). This Lisp file is aware of SLIME, so anything you type can easily be validated by the running Lisp. Tab completion, class inspection, interactive testing, etc. are all available.

As an example, type something like (+ 1 2) and press C-x C-e. You will see the result, as evaluated by the running Lisp, at the bottom of the window. This lets you test individual expressions as you type them into the file.

The next step is to write a full function, perhaps:

(defun my-1+ (x)
    (+ x 1))

You can load this function into the running Lisp in a variety of ways; I usually use C-M-x. You can now change back to the REPL buffer (C-x b *slime-repl sbcl* or similar) and type (my-1+ 42) and see the result 43 printed.

Another way to bring the functions into the running Lisp is to compile and load the whole file with C-c C-k.

Anyway, that's the basics of using SLIME and Emacs. There are obviously many more features available, but this should give you a taste of Lisp programming with SLIME. One last thing I'll mention, Emacs is largely self-documenting, so if you want to learn more, Emacs can help you. While in your Lisp buffer, you can type C-h m to get a full list of commands you can use while editing Lisp. You can click the links to get more information about each function.

Have fun!

Answer 5

Don't give up Vi/Vim just because a large percentage of people like Slime.

I've written about this before here on SO. Check these out:

• Using Vim for Lisp development
• https://stackoverflow.com/questions/451329/what-is-the-preferred-way-to-run-lisp-web-application/558329#558329
• Best Common Lisp IDE
• Are there any good editors for Lisp programming, other than Emacs?

I'll be happy to answer specific questions here.

Answer 6

I can say that Emacs is a good environment for writing Lisp, since I used it in college to that end. The *scratch* buffer provides a good place for test code. The compiler docs should say how to call them, so you can write out your files to disk and then run them in a shell window, or use one of Emacs' modes to integrate the edit-compile-and-run. (Sorry I'm not more specific, it's been 15 years.)