Lisp environment with Emacs - slime not loading

Question

I was wondering whether someone could help me spot the problem on installing slime on Emacs. I have Ubuntu 12.04.

I was following this tutorial (I have to use this one):

http://emergent-languages.org/Babel2/linux.html

and I am stuck at point 6. Basically, the messages in Emacs say

Loading cua-base...done

Loading paren...done

Polling "/tmp/slime.3213" .. 1 (Abort with `Mx slime-abort-connection'.)

For information about GNU Emacs and the GNU system, type Ch Ca.

(New file)

Polling "/tmp/slime.3213" .. 2 (Abort with `Mx slime-abort-connection'.)

Failed to connect to Swank: inferior process exited

The tutorial says "do not use the slime that comes with Emacs", and I have followed their precise instructions. I have the donwloaded folders (ccl and slime) in /usr/local/share as they suggest, updating the file ~/.emacs as they do. I have also tried removing and installing emacs again, to no avail.

Answer 1

Here's a bit hackish way to try to diagnose:

1. Install tcpdump (something like sudo apt-get install tcpdump on Debian-like system).
2. In Emacs, Mx shell
3. In the shell buffer type this: sudo tcpdump -i lo -A -q -nn -t
4. Mx slime .
5. You will have to see output similar to the below, but probably probably different.

---

[sudo] password for wvxvw: 
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on lo, link-type EN10MB (Ethernet), capture size 65535 bytes
IP 127.0.0.1.36590 > 127.0.0.1.59445: tcp 0
E..<%.@.@..............5.5...........0.........
.H..........
IP 127.0.0.1.59445 > 127.0.0.1.36590: tcp 0
.....0.........
.H...H......
IP 127.0.0.1.36590 > 127.0.0.1.59445: tcp 0
72o....V.(.....
.H...H..
IP 127.0.0.1.36590 > 127.0.0.1.59445: tcp 66
72o....V.j.....
.H...H..00003c(:emacs-rex (swank:connection-info) "COMMON-LISP-USER" t 2)

IP 127.0.0.1.59445 > 127.0.0.1.36590: tcp 0
E..4..@.@............5..72o..5.O...V.(.....
.H...H..
IP 127.0.0.1.59445 > 127.0.0.1.36590: tcp 1314
E..V..@.@............5..72o..5.O...V.K.....
.I...H..00051C(:return (:ok (:pid 8924 :style :spawn :encoding (:coding-systems

Post your output, this way we'll know on what stage of connection it failed to connect. What the above does: it shows all the traffic going on your local loopback interface. So you want to make sure you aren't posting anything confidential :)

---

to make sure you can create files in your home directory:

Tell us what you see when you do:

$ ls -la ~ | grep ' \.$' | awk '{ print $1 }'

This should be: drwx------. But if it isn't, do:

$ chmod u+rwx ~

If the directory .cache is already there, do the same procedure for it too, ie make sure that the owner of the directory can read, write and execute (opening directories requires execute permissions).