[slime-devel] Uh, (require 'slime) errors out

[Peter Seibel]

I can no longer (require 'slime) because I get an error "Not
connected". I'm trying to track it down from the backtrace (see below)
but since it just started happening I'm assuming this is due to some
recent change and perhaps the author of said change will know right
away what's wrong.

-Peter

P.S. I'm a CVS idiot--how do I see what changes have been made
recently to a given file?

P.P.S Here's the backtrace:

Debugger entered--Lisp error: (error "Not connected.")
  signal(error ("Not connected."))
  error("Not connected.")
  (cond ((null conn) (error "Not connected.")) ((not ...) (error "Connection closed.")) (t conn))
  (let ((conn ...)) (cond (... ...) (... ...) (t conn)))
  slime-connection()
  (or process (slime-connection) (error "No connection"))
  (process-buffer (or process (slime-connection) (error "No connection")))
  (set-buffer (process-buffer (or process ... ...)))
  (save-current-buffer (set-buffer (process-buffer ...)) slime-rex-continuations:connlocal)
  (with-current-buffer (process-buffer (or process ... ...)) slime-rex-continuations:connlocal)
  (slime-with-connection-buffer (process) slime-rex-continuations:connlocal)
  slime-rex-continuations()
  slime-busy-p()
  (null (slime-busy-p))
  (and (not (sldb-get-default-buffer)) (null (slime-busy-p)))
  slime-at-top-level-p()
  (progn (slime-at-top-level-p))
  (if (progn (slime-at-top-level-p)) (slime-print-check-ok check-name-14528) (cond (... ... ...) (t ... ...)) (when slime-test-debug-on-error (debug ...)))
  (let ((check-name-14528 "At the top level (no debugging or pending RPCs)")) (if (progn ...) (slime-print-check-ok check-name-14528) (cond ... ...) (when slime-test-debug-on-error ...)))
  (slime-check "At the top level (no debugging or pending RPCs)" (slime-at-top-level-p))
  slime-check-top-level()
  eval-buffer(#<buffer  *load*> nil "slime" nil t)
  load-with-code-conversion("/home/peter/cvs/slime/slime.el" "slime" nil t)
  require(slime)
  eval((require (quote slime)))
  eval-last-sexp-1(nil)
  eval-last-sexp(nil)
  call-interactively(eval-last-sexp)

-- 
Peter Seibel                                      peter at javamonkey.com

         Lisp is the red pill. -- John Fraser, comp.lang.lisp