Update:
Yes, updating to the latest version worked. Belated thanks to Helmut for that.
On my AWS EC2, yum install emacs would not go to the latest version, but one before the fixes described below as coming after Dec. 2010.
I followed these instructions to build the latest (thanks to Hans (as usual) for these).
build emacs from source, it should be nothing more than getting and unpacking the tarball, then:
sudo yum remove emacs # i think, to remove the old emacs sudo yum install -y ncurses-devel ./configure --prefix=/usr/local --with-xpm=no make sudo make install
Then '/usr/local/bin/emacs' to run it. (It was in my path, but for some reason I could not just do 'emacs' until I logged out and logged back in again.)
Hope this helps anyone else that might feel stuck.
-Mark
On 11/11/2011 3:38 AM, Helmut Eller wrote:
- Mark H. David [2011-11-11 05:42] writes:
I keep getting this error in SLIME/emacs/AWS EC2
Anyone familiar with this? If I try again and again, it goes away and all works well until the next time or the time after that.
There is a problem with older Emacsen that causes a similar problem. When such an old Emacsen receives a signal during connect, Emacs closes the connection and tries to reconnect. Newer Emacs versions wait until the file descriptor for the socket becomes readable. I think that problem was fixed in versions after Dec. 2010.
Helmut
slime-devel site list slime-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/slime-devel