slime error in lispbox,lispstick.

slime error in lispbox,lispstick.

[eugene1560233]

In order to learn commonlisp,I download lispbox first then lispstic.Both of them are  a package of Emacs with SLIME, Quicklisp, and CCL.But when I try to open it on windows,the same error happened:
Debugger entered: (("Error in timer" slime-attempt-connection (#<process inferior-lisp> nil 23) (file-error "make client process failed" "too many open files" :name "SLIME Lisp" :buffer nil :host "127.0.0.1" :service 5290 :nowait nil)))
  (condition-case data (apply fun args) ((debug error) (debug nil (list "Error in timer" fun args data))))
  slime-timer-call(slime-attempt-connection #<process inferior-lisp> nil 23)
  apply(slime-timer-call (slime-attempt-connection #<process inferior-lisp> nil 23))
  byte-code("r\301\b\302H\b\303H\"\210)\301\207" [timer apply 5 6] 4)
  timer-event-handler([t 21610 41877 903000 nil slime-timer-call (slime-attempt-connection #<process inferior-lisp> nil 23) nil 0])

Re: slime error in lispbox,lispstick.

[Alexis]

eugene1560233@gmail.com writes:

> In order to learn commonlisp,I download lispbox first then lispstic.

Assuming you downloaded Lispbox from here:

http://common-lisp.net/project/lispbox/

then it seems the latest release of Lispbox was 3.5 years ago. This
means Lispbox uses a version of Emacs (23.2) which not only doesn't
include 3.5 years' worth of bug fixes, but which also doesn't include
`package.el` by default - and `package.el` makes it /much/ easier (in my
experience) to install the latest version of SLIME (as well as many
other dev-related packages).

So i feel you would probably be better off downloading Emacs
24.4, using the Emacs packaging system to install SLIME, and then
customising further from there.


Alexis.

Re: slime error in lispbox,lispstick.

[eugene1560233]

It is true that the latest release of Lispbox was 3.5 years ago,but lispstick has a recen t release and it uses Emacs(24.3).The same error happened after I run them on windows.So maybe it is a slime error.Hope for someone facing the same problem can debug it.