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

[slime-devel] C-g after C-c ==> debugger
by Chisheng Huang 04 Aug '04

04 Aug '04

Typing C-g after C-c in a buffer editing a Lisp file will get a *sldb* buffer to show up: Error in function NIL: Interrupt from Emacs [Condition of type SIMPLE-ERROR] Restarts: 0: [CONTINUE] Continue from interrupt. 1: [ABORT] Abort handling SLIME request. 2: [ABORT] Return to Top-Level. Backtrace: ... I find myself getting thrown into a debugger this way quite a few times everyday. Could someone make Slime handle C-g better after a C-c? Thanks a lot. Best, -cph

5 8

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

04 Aug '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.494 slime/ChangeLog:1.495 --- slime/ChangeLog:1.494 Sun Aug 1 22:27:07 2004 +++ slime/ChangeLog Tue Aug 3 23:23:30 2004 @@ -1,3 +1,11 @@ +2004-08-04 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * slime.el: (slime-mode-map, slime-repl-mode-map) + (slime-repl-read-mode-map): Remove the binding for C-c C-g. C-c + C-b is now the default interrupt key. + (slime-list-repl-short-cuts): Don't trash the shortcut-table: copy + it before sorting. (Thanks to Mark Simpson.) + 2004-08-02 Luke Gorrie <luke(a)bluetail.com> * slime.el (slime-connect): Shorten the welcome message by leaving

1 0

[slime-devel] Shortcuts disappearing?!
by Person or Persons Unknown 04 Aug '04

04 Aug '04

(I just tracked the reason for a problem i have been seeing... hopefully this is the right place to provide bug reports and patches.) I started using SLIME at the 1.0 alpha stage and just updated to 1.0 beta tonight and still have a problem with shortcuts disappearing. The session will start out with all the shortcut commands but after some actions i will only have a short list of shortcut commands. I can consistently cause the problem by starting up SLIME, bringing up the shortcut help (via ,help) and then trying to do it again (i actually lose the help short cut so it fails! ,? will show two or three shortcuts now). The problem seems to be coming from the use of SORT* in SLIME-LIST-REPL-SHORT-CUTS. SORT* is a destructive function so the SLIME-REPL-SHORTCUT-TABLE is being trashed. Changing the code to call COPY-SEQUENCE on SLIME-REPL-SHORTCUT-TABLE before calling SORT* seems to do the trick. Thanks for SLIME, it is really slick! -Mark Simpson

2 1

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 03 Aug '04

03 Aug '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.488 slime/ChangeLog:1.489 --- slime/ChangeLog:1.488 Mon Jul 26 04:50:19 2004 +++ slime/ChangeLog Wed Jul 28 14:15:30 2004 @@ -1,3 +1,18 @@ +2004-07-28 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * slime.el (slime-eval-feature-conditional): Treat uppercase + operators NOT, AND, OR correctly. + (sldb-find-buffer): Remove killed buffers. + (sldb-quit): Raise an error if the RPC returns. + (slime-expected-failures): Delete unused function. + (complete-symbol): Test completion of + swank::compile-file. LispWorks has extra completions for + cl::compile-file. + (arglist): Test arglist of method cl:class-name. Add enough + regexpery to pass the test in most implementations. + + * swank-sbcl.lisp (list-callers, list-callees): Implemented. + 2004-07-26 Luke Gorrie <luke(a)bluetail.com> * slime.el (slime-first-change-hook): Add `save-match-data' to

3 5

[slime-devel] swank/xref and slime-load-file
by Jonathan Meeks 02 Aug '04

02 Aug '04

I think there is a bug in slime-load-file. I have noticed that when a file has its *.lisp extension in the parameter to slime-load-file, swank/xref is not able to find its callees (with slime-list-callees). When called interactively, the extension is stripped and slime-list-callees works. So, shouldn't the extension be stripped by slime-load-file when called non-interactively, as well? --Jonathan Meeks

3 3

[slime-devel] Extra Swank threads after slime-disconnect
by Alan Caulkins 02 Aug '04

02 Aug '04

Hello list, To start, I'm new to the list, and I'd like to congratulate everyone on creating such a wonderful piece of software. I've been continually impressed by SLIME ever since I started keeping up with it a few months ago. However, I think I've found a bug in Swank's spawn connection-style. I've been connecting to an already-running sbcl (on Linux) as per the instructions found on on Bill Clemenson's weblog, linked from CLiki's SLIME-HOWTO page. fatman@hubris:~$ sbcl --load slime.lisp This is SBCL 0.8.13, an implementation of ANSI Common Lisp. More information about SBCL is available at <http://www.sbcl.org/>. . <snip> . ;; Swank started at port: 4005. * My slime.lisp is simple: (load "lib/emacs/slime/swank-loader.lisp") (swank::create-swank-server 4005 :spawn #'swank::simple-announce-function t) Before connecting to Swank for the first time, there are 2 sbcl threads running: fatman@hubris:~$ ps -e | grep sbcl 9831 pts/0 00:00:04 sbcl 9832 pts/0 00:00:00 sbcl After running (slime-connect "localhost" 4005), we also see the new reader, control, and repl threads: fatman@hubris:~$ ps -e | grep sbcl 9831 pts/0 00:00:04 sbcl 9832 pts/0 00:00:00 sbcl 9844 pts/0 00:00:00 sbcl 9845 pts/0 00:00:00 sbcl 9846 pts/0 00:00:00 sbcl CL-USER> (in-package swank) #<PACKAGE "SWANK"> SWANK> (mapcar (lambda (c) (list (connection.control-thread c) (connection.reader-thread c) (connection.repl-thread c))) *connections*) ((9844 9845 9846)) But, after running (slime-disconnect), only the reader thread has terminated: fatman@hubris:~$ ps -e | grep sbcl 9831 pts/0 00:00:04 sbcl 9832 pts/0 00:00:00 sbcl 9844 pts/0 00:00:00 sbcl 9846 pts/0 00:00:00 sbcl With each successive connection and disconnection, two more threads are added. I suspect that's not the intended behavior. :) First of all, does this happen to anyone else? I'm using the laterst release of SBCL and the 1.0 Alpha release of SLIME, but some of my system libraries are pathetically out of date. I wouldn't be surprised to learn that my own system is the problem. Secondly, assuming this is a bug, I have come up with a fix. I simply defined a function for the :cleanup slot in the connection struct. My fix is decidedly simple-minded - I just kill the other two threads. It seems to work, but I have no idea if those threads were left alive for some reason, or if there is a better way to get them to terminate. Also, I'm still very new to the Lisp game, and although I've tried to honor your indirection and abstractions, I have no idea if I succeeded. -Alan PS- I tried to make the following diff from the current CVS instead of 1.0alpha, but I got these kind of errors on the sbcl console when the connection was closed: debugger invoked on a UNDEFINED-FUNCTION in thread 10396: The function :DEBUG is undefined. Linux: The ultimate video game. fatman@hubris:~/lib/emacs$ diff slime.alan/swank.lisp slime-1.0alpha/swank.lisp 488,491d487 < (defun cleanup-connection-threads (connection) < (kill-thread (connection.control-thread connection)) < (kill-thread (connection.repl-thread connection))) < 599,600c595 < :serve-requests #'spawn-threads-for-connection < :cleanup #'cleanup-connection-threads)) --- > :serve-requests #'spawn-threads-for-connection))

2 2

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 02 Aug '04

02 Aug '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.493 slime/ChangeLog:1.494 --- slime/ChangeLog:1.493 Sat Jul 31 23:46:48 2004 +++ slime/ChangeLog Sun Aug 1 22:27:07 2004 @@ -1,3 +1,31 @@ +2004-08-02 Luke Gorrie <luke(a)bluetail.com> + + * slime.el (slime-connect): Shorten the welcome message by leaving + out the port number (which is displayed in the REPL anyway). This + avoids line-wrapping some messages of encouragement. + + * swank.lisp (with-buffer-syntax): Don't bind *readtable* to + *buffer-readtable* if they are already EQ. When we shadow this + binding the user can't assign *readtable* from the REPL so it's + best avoided when possible. + + * swank-allegro.lisp: Removed fwrapper-based code for inheriting + "swankiness" to newly spawned threads. This was fighting the + system and not the right thing. + + * slime.el (slime-choose-overlay-region): Tweaked the + multiline-annotation-avoidance code to work with forms not + starting with an open-paren, e.g. `(..) or #'(..). + (slime-update-modeline-package): New configurable. Non-nil (the + default) means update the Lisp package in the modeline using an + idle timer. + (slime-repl-send-input): Make the `slime-repl-old-input' property + cover the whole input (including newline) so that pressing RET on + the end of an input line works. + Use a unique integer as the value of this property to distinguish + adjacent inputs. + (slime-current-package): Deal with narrowing. + 2004-08-01 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> * swank-allegro.lisp (swank-compile-string): Use a temporary file @@ -25,20 +53,6 @@ * swank-backend.lisp (sldb-condition): Show the original condition in the message. - -2004-07-30 Luke Gorrie <luke(a)bluetail.com> - - * slime.el (slime-choose-overlay-region): Tweaked the - multiline-annotation-avoidance code to work with forms not - starting with an open-paren, e.g. `(..) or #'(..). - (slime-update-modeline-package): New configurable. Non-nil (the - default) means update the Lisp package in the modeline using an - idle timer. - (slime-repl-send-input): Make the `slime-repl-old-input' property - cover the whole input (including newline) so that pressing RET on - the end of an input line works. - Use a unique integer as the value of this property to distinguish - adjacent inputs. 2004-07-28 Helmut Eller <e9626484(a)stud3.tuwien.ac.at>

1 0

[slime-devel] Package gets lost in narrowed buffer
by Alain.Picard＠memetrics.com 02 Aug '04

02 Aug '04

Dear Slimers, This might be a strange way of working, but I quite often "narrow" my lisp buffers, to work on only a few definitions. Recently, SLIME seems to lose track of the package in that situation and evaluates the C-cC-c requests in the USER package, instead of the correct package. Cheers,

2 1

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 01 Aug '04

01 Aug '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.492 slime/ChangeLog:1.493 --- slime/ChangeLog:1.492 Fri Jul 30 14:41:25 2004 +++ slime/ChangeLog Sat Jul 31 23:46:48 2004 @@ -1,3 +1,15 @@ +2004-08-01 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * swank-allegro.lisp (swank-compile-string): Use a temporary file + and set excl::*source-pathname* manually. This way we can find + the source buffer of functions compiled with C-c C-c. + (call-with-temp-file, compile-from-temp-file): New functions. + (list-callers, function-callers, in-constants-p) + (map-function-constants): Implements list callers by groveling + through the constants pools of named functions. + + * swank-lispworks.lisp: Minor refactoring. + 2004-07-30 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> * slime.el (slime-connection): Say "No default connection @@ -10,7 +22,10 @@ * swank-cmucl.lisp (call-with-debugging-environment): Only handle DI::UNHANDLED-CONDITION not all DI:DEBUG-CONDITIONs. - + + * swank-backend.lisp (sldb-condition): Show the original condition + in the message. + 2004-07-30 Luke Gorrie <luke(a)bluetail.com> * slime.el (slime-choose-overlay-region): Tweaked the

1 0