July 2004 - slime-devel - mailman3.common-lisp.net

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 23 Jul '04

23 Jul '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.483 slime/ChangeLog:1.485 --- slime/ChangeLog:1.483 Wed Jul 21 12:56:54 2004 +++ slime/ChangeLog Thu Jul 22 09:55:26 2004 @@ -1,3 +1,13 @@ +2004-07-22 Luke Gorrie <luke(a)bluetail.com> + + * swank.lisp (carefully-find-package): Return *BUFFER-PACKAGE* if + no other package can be found. This is reverting a previous change + that broke completion in buffers with no known package. + + * slime.el (slime-maybe-start-lisp): Check that *inferior-lisp* + exists /and/ has a running process. Fixes a startup problem if + your inferior-lisp has died and you want to restart SLIME. + 2004-07-21 Luke Gorrie <luke(a)bluetail.com> * slime.el (slime-sync-package-and-default-directory): Sync

1 0

[slime-devel] nightly build
by Jeff Bowman 23 Jul '04

23 Jul '04

I am behind a firewall that prevents cvs from coming in. I have downloaded the slime-1.0alpha.tar.gz file and am using it, but I noticed one of the problems I'm having is mentioned in the list as being fixed. So my question is: is there a nightly build mechanism in place where I can download a more current version of slime than the tarball, or is the tarball contents updated frequently so I can get the fix? [RE: Symbol Completion Broken (CLISP)] Thanks! This is a great tool! Jeff

2 1

[slime-devel] Symbol completion broken (CLISP)
by Steven E. Harris 22 Jul '04

22 Jul '04

Using CLISP with SLIME updated from CVS as of 21 June 2004, symbol completion coaxed by M-Tab (`slime-complete-symbol') no longer produces anything useful. If I type (with-o in a buffer in SLIME mode connected to a CLISP repl and hit M-Tab, SLIME reports in the minibuffer [Can't find completion for "with-o"] and refuses to either complete or suggest completions for the partial symbol. This used to work as of about two weeks ago, but I can't recall when the exact last time I tested this was. -- Steven E. Harris

2 2

[slime-devel] Uh, (require 'slime) errors out
by Peter Seibel 22 Jul '04

22 Jul '04

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(a)javamonkey.com Lisp is the red pill. -- John Fraser, comp.lang.lisp

5 5

[slime-devel] Slime cannot connect to ACL6.2 win32
by Thomas Schilling 22 Jul '04

22 Jul '04

The exact error message is: (stream/warning) failure to open network stream to host "localhost" for service "4005" Took a look at the changelog--Luke, something to confess? The relevant init.el part: ;; start up slime (global-set-key [(f5)] '(lambda () (interactive) (shell-command "c:/programme/acl62-demo/allegro-ansi.exe +B +cm -L ~/slime.lisp&") (sleep-for 3) (slime-connect "localhost" 4005) (cd "~/Eigene Dateien/"))) and ~/slime.lisp is: (load "~/Eigene Dateien/devel/lisp/slime/swank-loader.lisp") (swank::create-swank-server 4005 :spawn #'swank::simple-announce-function t) -- ,, \../ / <<< The LISP Effect |_\\ _==__ __ | |bb| | _________________________________________________

2 10

[slime-devel] can't restart lisp/slime in the same emacs session
by Chisheng Huang 22 Jul '04

22 Jul '04

After doing a cvs update today (2004-07-21 PDT), I'm having trouble restarting Lisp/Slime: 1. "M-x slime" to get a *slime-repl[1]* buffer 2. Type (quite) in *slime-repl[1]* buffer and this message shows up in the mini buffer: error in process sentinel: Connection closed 3. Doing "M-x slime" again will not get a *slime-repl[1]* buffer and the following message shows up in the mini buffer: No Lisp subprocess: see variable `inferior-lisp-buffer'. I hope I do not have to mess with inferior-lisp-buffer everytime I restart Lisp/Slime. I'm using CMUCL-19a-pre3 (x86, Linux) and GNU Emacs 21.2.1. Best, -cph

2 2

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 22 Jul '04

22 Jul '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.481 slime/ChangeLog:1.483 --- slime/ChangeLog:1.481 Mon Jul 19 17:53:57 2004 +++ slime/ChangeLog Wed Jul 21 12:56:54 2004 @@ -1,3 +1,12 @@ +2004-07-21 Luke Gorrie <luke(a)bluetail.com> + + * slime.el (slime-sync-package-and-default-directory): Sync + `default-directory' in the REPL buffer too. + (slime-set-state): Convenience function for setting a connection's + state-name and updating the modeline if appropriate. This function + is called in the right places. + (slime-to-lisp-filename): Use `expand-file-name'. + 2004-07-20 Luke Gorrie <luke(a)bluetail.com> * slime.el (slime-repl-update-banner): Restore old behaviour of @@ -86,6 +95,9 @@ * slime.el (package-updating): Fixing this and other tests I broke with my change to how emacs keeps track of the package prompt string. + (arglist): Fix an test failure under Allegro due to a slight + difference in the way EXCL:ARGLIST returns arglist (no default + values of &optional parameters) 2004-07-16 Luke Gorrie <luke(a)bluetail.com>

1 0

[slime-devel] SLIME for newbies, or should the REPL and SLDB have a menu too?
by Dirk Gerrits 21 Jul '04

21 Jul '04

When SLIME is loaded, and you're editing a Lisp file, the menubar shows a SLIME menu where you can go for the less often used features or forgotten keybindings. The REPL and SLDB, however, lack such menus. If it's not too much trouble, I think these should be added. It may make things (even) more accessible to beginning SLIMErs. (And people like me who forget the keybindings all the time until they become firmly engraved in muscle memory when they have been used a bazillion times. ;)) Regards, Dirk Gerrits

2 1

[slime-devel] Really slow to interrupt in Allegro 6.2
by Peter Seibel 21 Jul '04

21 Jul '04

So when I use C-c C-c (slime-interrupt) to try to interrupt a long-running computation in SLIME it sometimes takes a really long time (order 10-60 seconds) before the debugger pops up. I've also noticed that if I do something that generates an error that will contain a lot of output (such as saying (boundp *y*) instead of (boundp '*y*) when *y* is list of several thousand standard-objects) then it also takes a really long time for the debugger to come up. I'm running Allegro 6.2 on GNU/Linux. Haven't had a chance to try this out in other Lisps but thought I'd throw it out there in case anyone has seen a similar thing or has any ideas how to speed things up. -Peter -- Peter Seibel peter(a)javamonkey.com Lisp is the red pill. -- John Fraser, comp.lang.lisp

2 3

[slime-devel] Slime+cmucl+McClim problem
by Thibault Langlois 20 Jul '04

20 Jul '04

Hello, I could not find a solution for the following problem. When I start a McClim application from slime REPL it uses 100% of cpu. I have done what is suggested in the McCLIM instalation tips. I tried to put (mp::startup-idle-and-top-level-loops) in my init.lisp file, i tried to use (setq slime-multiprocessing t) in my .emacs without success. I think the problem is on the slime side. When I start lisp in a xterm there is no problem. Finally I tried to make a cmucl image with the :init-function argument set to mp::startup-idle-and-top-level-loops. Agains it works fine when used from a xterm but does not when used from slime. I use latest (yesterday) cvs slime, latest McCLIM and cmucl 19a (pre) on linux FC2. Any suggestion ? Thanks. Thibault Langlois

2 2