>>16
Depends on the OS. Usually you first install Emacs, then you download SLIME from CVS (or get a cvs snapshot). After that you write your
.emacs, if you haven't written one already, this means writing something like:
(setq slime-lisp-implementations
'((sbcl ("sbcl") :coding-system utf-8-unix)
(ccl ("path/to/wx86cl"))
(clisp ("path/to/clisp")
...)))
(setq slime-net-coding-system 'utf-8-unix)
(add-to-list 'load-path "path/to/slime/")
(add-to-list 'load-path "path/to/paredit/and/other/stuff/you/want/to/load")
(require 'slime)
(slime-setup '(slime-fancy slime-asdf slime-banner slime-presentation-streams slime-xref-browser slime-compiler-notes-tree slime-indentation slime-mrepl slime-sbcl-exts))
or merely
(require 'slime-autoloads) and
(slime-setup)
(defun slime-lisp-implementations-fun (name)
(eval `(defun ,name ()
(interactive)
(apply 'slime-start
(list* :buffer (concat "*inferior-lisp-"
,(symbol-name name) "*")
(slime-lookup-lisp-implementation
slime-lisp-implementations ',name))))))
(mapcar 'slime-lisp-implementations-fun (mapcar 'car slime-lisp-implementations))
(autoload 'paredit-mode "paredit" "Minor mode for pseudo-structurally editing Lisp code." t)
(add-hook 'lisp-mode-hook (lambda () (paredit-mode +1))) ; always default
I also have a lot of other stuff in there like various key-chords, various settings for all kinds of Emacs, SLIME, ...-related things, hooks, hyperspec path, indentation settings, color scheme and so on. Just read the documentation or source code for the things that you want to install or customize.
Here's some short tutorial for setting up SLIME, I used something like it when I first set Emacs+SLIME+ASDF up:
http://paste.lisp.org/display/89718