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@javamonkey.com writes:
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.
Uh, I'm not sure what happened there. Either I hadn't checked in something I thought I did or someone half backed it out or CVS screwed me or I'm just an idiot. Anyway I'm okay now. At any rate, a change I thought I had checked in (for the Allegro test failures) the other day is no longer (or was never) in CVS so I'm putting it back in.
-Peter
On Wed, 21 Jul 2004, Peter Seibel wrote:
P.S. I'm a CVS idiot--how do I see what changes have been made recently to a given file?
Me too. So I use
http://www.common-lisp.net/cgi-bin/viewcvs.cgi/slime/?sortby=date&cvsroo...
Click on a filename, not a revision number.
Andras
Peter Seibel peter@javamonkey.com writes:
P.S. I'm a CVS idiot--how do I see what changes have been made recently to a given file?
Another option is to subscribe to the slime-cvs mailing list, which sends commit log messages and diffs.
Paolo
Paolo Amoroso amoroso@mclink.it writes:
Peter Seibel peter@javamonkey.com writes:
P.S. I'm a CVS idiot--how do I see what changes have been made recently to a given file?
Another option is to subscribe to the slime-cvs mailing list, which sends commit log messages and diffs.
Or in Emacs press `C-x v l' for to see the CVS log. Another useful one is `C-x v g' (annotate) which shows the last time each line of the file was modified, who by, and colour-codes the lines according to age.