March 2005 - slime-devel - mailman3.common-lisp.net

[slime-devel] How to pretty-print debugger frames
by Paolo Amoroso 06 Mar '05

06 Mar '05

In past versions of SLIME, it was possible to make SLDB pretty-print debugger frames by setting SWANK:*SLDB-PRINT-PRETTY* or SWANK:*SLDB-PPRINT-FRAMES* to T. What is the current way of doing that? Paolo -- Lisp Propulsion Laboratory log - http://www.paoloamoroso.it/log

2 1

[slime-devel] slime-edit-definition woes
by Edi Weitz 06 Mar '05

06 Mar '05

Hi! One of the last CVS updates somehow managed to break slime-edit-definition for me. Sometimes, if I press M-. to go to a function's definition Emacs hangs completely, CPU load goes up to 100%, C-g doesn't work anymore, and I have to kill both Emacs and the Lisp to continue. Needless to say, this is highly annoying. I'd like to come up with a simple test case but unfortunately this only happens sometimes and when it happens it's too late to debug it. I've seen this with CMUCL 19a as well as with AllegroCL 7.0, Emacs is FSF 21.3 on Linux. Am I the only one? Thanks, Edi.

3 20

[slime-devel] Daily ChangeLog diff
by lgorrie＠common-lisp.net 05 Mar '05

05 Mar '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.620 slime/ChangeLog:1.621 --- slime/ChangeLog:1.620 Thu Mar 3 01:03:49 2005 +++ slime/ChangeLog Sat Mar 5 00:44:38 2005 @@ -1,3 +1,35 @@ +2005-03-05 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-net-sentinel): Always print a message when the + lisp disconnects. + (slime-inferior-lisp): Don't display the buffer. Let callers do + that. + (slime): Display the inferior buffer here. + (slime-quit-lisp, slime-quit-sentinel): Use set a special sentinel + and do most of the cleanups there. + (slime-repl-sayoonara): Use slime-quit-lisp. + (slime-restart-inferior-lisp, slime-restart-inferior-lisp-aux) + (slime-restart-sentinel): Use a special sentinel to restart + processes. + (slime-hide-inferior-lisp-buffer): Do the windows arrangement a + bit differently. Related to restart-lisp. + (slime-repl-buffer): Take the connection as second optional + argument. Useful for rearranging windows for dead processes. + + * swank-allegro.lisp (call-with-debugging-environment) + (find-topframe): Hide the first 2 frames. Those are created + by swank-internal functions. + +2005-03-04 Antonio Menezes Leitao <aml(a)gia.ist.utl.pt> + + * swank-allegro.lisp (process-fspec-for-allegro, toggle-trace): + Handle setf functions. + (tracedp): Fix free variable. + + * slime.el (slime-trace-query): The :defgeneric query was bogus. + (slime-extract-context): Don't skip over the method name if we are + already at the end of the name. + 2005-03-03 Nikodemus Siivola <tsiivola(a)cc.hut.fi> * swank-sbcl.lisp: Fixed for latest SBCL HEAD revision and

1 0

[slime-devel] Daily ChangeLog diff
by lgorrie＠common-lisp.net 03 Mar '05

03 Mar '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.618 slime/ChangeLog:1.620 --- slime/ChangeLog:1.618 Wed Mar 2 00:24:05 2005 +++ slime/ChangeLog Thu Mar 3 01:03:49 2005 @@ -1,3 +1,8 @@ +2005-03-03 Nikodemus Siivola <tsiivola(a)cc.hut.fi> + + * swank-sbcl.lisp: Fixed for latest SBCL HEAD revision and + temporarily backwards-compatible with the current release. + 2005-03-02 Marco Baringer <mb(a)bese.it> * swank-loader.lisp Look for a file in the same directory as

1 0

[slime-devel] Breakage with bleeding edge SBCL
by Nikodemus Siivola 03 Mar '05

03 Mar '05

Current CVS HEAD SBCL breaks Slime again. I cheerfully submit that this is "not SBCL's fault" as the interfaces that have changed were unexported and unsupported: 1) SB-DEBUG::PRINT-CODE-LOCATION-SOURCE-FORM was replaced by SB-DEBUG::CODE-LOCATION-SOURCE-FORM; do the printing as you please. 2) SB-DEBUG::PRINT-FRAME-CALL now takes a second required argument, the stream to print to. The attached patch should fixes things for both bleeding edge and older versions, but still uses the unexported interfaces and is hence liable to break again. :/ Cheers, -- Nikodemus Schemer: "Buddha is small, clean, and serious." Lispnik: "Buddha is big, has hairy armpits, and laughs."

2 4

[slime-devel] Problem with CLSQL
by Alan Shutko 03 Mar '05

03 Mar '05

I've found a problem when I try to C-c C-k a file which uses CLSQL's SQL reader syntax. The file compiles and loads fine outside of SLIME (with but a single warning) but when I C-c C-k, I get the message A CLSQL lisp code error occurred: bad expression syntax [Condition of type CLSQL-SYS:SQL-USER-ERROR] Restarts: 0: [ABORT] Abort SLIME compilation. [...] I seem to have tracked it down to swank-backend::read-source-form in swank-source-path-parser.lisp, but I'm not sure what to do. I'm using CLSQL 3.1.6, with SBCL and SLIME from CVS (current as of this message). Does anyone else use CLSQL and have an idea why this is failing? -- Alan Shutko <ats(a)acm.org> - I am the rocks. "So easy a child can do it" (child not included) (clsql:enable-sql-reader-syntax) (defun testme () (or nil [name])) (defun a (dummy) nil)

1 0

[slime-devel] Daily ChangeLog diff
by lgorrie＠common-lisp.net 02 Mar '05

02 Mar '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.617 slime/ChangeLog:1.618 --- slime/ChangeLog:1.617 Tue Mar 1 00:34:08 2005 +++ slime/ChangeLog Wed Mar 2 00:24:05 2005 @@ -1,3 +1,12 @@ +2005-03-02 Marco Baringer <mb(a)bese.it> + + * swank-loader.lisp Look for a file in the same directory as + swank-loader.lisp called site-init.lisp. If it exists we load that + instead of attempting to load ~/.swank.lisp. + (user-init-file): Superseded by load-user-init-file. + (load-user-init-file): New function. + (load-site-init-file): New function. + 2005-03-01 Helmut Eller <heller(a)common-lisp.net> * slime.el (slime-who-bindings): Bind who-specializes to C-c W a.

1 0

[slime-devel] Post 1.0 official release?
by Peter Seibel 02 Mar '05

02 Mar '05

Are there any plans for a 1.1 or 1.0.1 or whatever "official" release. (I think I've read all the SLIME messages that have come across the transom in recent months but I haven't been paying super close attention so may have missed an announcement or discussion.) I ask because after the 25th when I turn in my last page proof, I'm going to be spending a month getting together a Lisp in a Box distro that includes the code from my book. And I seem to recall that SLIME 1.0 doesn't work with the newer versions of SBCL (because of the Unicode support added to SBCL?). So from my purely selfish point of view, now would be an excellent time for an official upgrade of SLIME. If that's not going to happen I'll probably build a LIAB distro with some snapshot of CVS SLIME that seems to work well. Also, if there are specific things that need to happen before a 1.1 or 1.0.1 release of SLIME, let me know; maybe I can tackle some of them. -Peter -- Peter Seibel peter(a)javamonkey.com Lisp is the red pill. -- John Fraser, comp.lang.lisp

5 8

[slime-devel] .swank.lisp
by Peter Seibel 01 Mar '05

01 Mar '05

I'm working on my Lisp in a Box distro and I want to make SLIME load .swank.lisp from somewhere other than USER-HOMEDIR-PATHNAME. I'm not sure what the best way to do that is. Looks like the simplest least intrusive way would be to change swank-loader's USER-INIT-FILE to something like: (defun user-init-file () "Return the name of the user init file or nil." (probe-file (merge-pathnames (or (SOME-MAGIC-HERE) (user-homedir-pathname)) (make-pathname :name ".swank" :type "lisp")))) Do folks have any objection to this? And if not, does anyone have any ideas about what SOME-MAGIC-HERE should do? Ideally I'd like something that will work on OS X, GNU/Linux, and Windows. Or another way to achieve my goal, is to have swank-loader load a file, site-swank.lisp if it exists and to define a variable which will turn off loading of the user-init-file. Then I can build a site-swank.lisp that does the initialization I need for Lispbox and then disable loading of the users .swank.lisp. (I want to do this because the whole point of my Lispbox distro is to provide a stable a predictable environment. -Peter -- Peter Seibel peter(a)gigamonkeys.com Lisp is the red pill. -- John Fraser, comp.lang.lisp

3 5

[slime-devel] Daily ChangeLog diff
by lgorrie＠common-lisp.net 01 Mar '05

01 Mar '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.616 slime/ChangeLog:1.617 --- slime/ChangeLog:1.616 Thu Feb 24 19:18:10 2005 +++ slime/ChangeLog Tue Mar 1 00:34:08 2005 @@ -1,3 +1,35 @@ +2005-03-01 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-who-bindings): Bind who-specializes to C-c W a. + (slime-extract-context): Renamed from name-context-at-point. + (slime-beginning-of-list): Renamed from out-first. + (slime-slime-parse-toplevel-form): Renamed from definition-name. + (slime-arglist-specializers): Renamed from parameter-specializers. + (slime-toggle-trace-function, slime-toggle-trace-defgeneric) + (slime-toggle-trace-defmethod, slime-toggle-trace-maybe-wherein) + (slime-toggle-trace-within): Deleted. Everything is now handled + by slime-trace-query. + (slime-calls-who): For symmetry with silme-who-calls. + (slime-edit-definition-with-etags): Better intergration with TAGS. + (slime-edit-definition-fallback-function): Mention it in the + docstring. + + * swank-backend (calls-who, toggle-trace): New functions. + (toggle-trace-function, toggle-trace-generic-function-methods, + (toggle-trace-method, toggle-trace-fdefinition-wherein): Replaced + by toggle-trace. + + * swank.lisp (*sldb-printer-bindings*, *swank-pprint-bindings*): + New variables. The alists replace the variables which where + previously hidden with the define-printer-variables macro. + (define-printer-variables, with-printer-settings): Deleted, + because the variable names where not visible in the source code. + (swank-toggle-trace): Renamed from toggle-trace-fdefinition. + + * swank-cmucl.lisp, swank-lispworks, swank-sbcl.lisp, + swank-allegro.lisp (toggle-trace): Update tracing code for new + interface. + 2005-02-24 Helmut Eller <heller(a)common-lisp.net> * slime.el (slime-dispatch-event): Add :eval-no-wait and :eval

1 0