slime-devel August 2008

slime-devel@common-lisp.net

39 participants
73 discussions

[slime-devel] patch to swank-loader.lisp
by B.Scott Michel 17 Aug '08

17 Aug '08

Please find attached that correct's a sbcl style warning (init is referenced before it is defined). I'm currently hacking on the cusp environment for Eclipse and attempting to keep sbcl's style warnings and n00bie questions to a minimum. V/R and R/ Scott Michel Index: swank-loader.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/swank-loader.lisp,v retrieving revision 1.87 diff -u -r1.87 swank-loader.lisp --- swank-loader.lisp 12 Aug 2008 17:54:44 -0000 1.87 +++ swank-loader.lisp 14 Aug 2008 02:50:04 -0000 @@ -226,10 +226,6 @@ (eval `(pushnew 'compile-contribs ,(q "swank::*after-init-hook*"))) (funcall (q "swank::init"))) -(defun dump-image (filename) - (init :setup nil) - (funcall (q "swank-backend:save-image") filename)) - (defun init (&key delete reload load-contribs (setup t)) (when (and delete (find-package :swank)) (mapc #'delete-package '(:swank :swank-io-package :swank-backend))) @@ -241,3 +237,7 @@ (compile-contribs :load t)) (when setup (setup))) + +(defun dump-image (filename) + (init :setup nil) + (funcall (q "swank-backend:save-image") filename))

2 1

[slime-devel] xref issue
by Carlos Konstanski 16 Aug '08

16 Aug '08

I've been seeing this problem the last few days when using M-. to follow a symbol's definition: Debugger entered--Lisp error: (wrong-type-argument stringp nil) set-buffer(nil) (save-current-buffer (set-buffer standard-output) (prog1 (progn ... ... ... ... ...) (assert ...) (setq buffer-read-only t) (slime-init-popup-buffer vars%))) (with-current-buffer standard-output (prog1 (progn ... ... ... ... ...) (assert ...) (setq buffer-read-only t) (slime-init-popup-buffer vars%))) (let* ((vars% ...) (standard-output ...)) (with-current-buffer standard-output (prog1 ... ... ... ...))) (slime-with-popup-buffer (xref-buffer-name% package t emacs-snapshot) (slime-xref-mode) (slime-set-truncate-lines) (setq slime-popup-buffer-quit-function (quote slime-xref-quit)) (erase-buffer) (prog1 (progn ... ... ... ...) (assert ...) (shrink-window-if-larger-than-buffer))) (let ((xref-buffer-name% ...)) (slime-with-popup-buffer (xref-buffer-name% package t emacs-snapshot) (slime-xref-mode) (slime-set-truncate-lines) (setq slime-popup-buffer-quit-function ...) (erase-buffer) (prog1 ... ... ...))) (slime-with-xref-buffer (type symbol package emacs-snapshot) (slime-insert-xrefs xrefs) (goto-char (point-min)) (forward-line) (skip-chars-forward " ")) (if (null xrefs) (message "No references found for %s." symbol) (setq slime-next-location-function (quote slime-goto-next-xref)) (slime-with-xref-buffer (type symbol package emacs-snapshot) (slime-insert-xrefs xrefs) (goto-char ...) (forward-line) (skip-chars-forward " "))) slime-show-xrefs((("/home/ckonstanski/IandC/dev/svn/iclisp/araneida/web/graph/tracker-graph.lisp" ("(DEFGENERIC PLOT-GRAPHS (TRACKER-GRAPH ROOT-DIR))" ...) ("(DEFMETHOD PLOT-GRAPHS TRACKER-GRAPH T)" ...))) definition "plot-graphs" "#:iclisp") (cond ((null xrefs) (error "No known definition for: %s (in %s)" name ...)) (1loc (slime-push-definition-stack) (slime-pop-to-location ... where)) ((slime-length= xrefs 1) (error "%s" ...)) (t (slime-show-xrefs file-alist ... name ...))) (let* ((--cl-rest-- ...) (1loc ...) (file-alist ...)) (cond (... ...) (1loc ... ...) (... ...) (t ...))) (progn (let* (... ... ...) (cond ... ... ... ...))) (destructuring-bind (1loc file-alist) (slime-analyze-xrefs xrefs) (cond (... ...) (1loc ... ...) (... ...) (t ...))) slime-edit-definition-cont((("(DEFGENERIC PLOT-GRAPHS (TRACKER-GRAPH ROOT-DIR))" (:location ... ... ...)) ("(DEFMETHOD PLOT-GRAPHS TRACKER-GRAPH T)" (:location ... ... ...))) "plot-graphs" nil) (or (run-hook-with-args-until-success (quote slime-edit-definition-hooks) name where) (slime-edit-definition-cont (slime-find-definitions name) name where)) slime-edit-definition("plot-graphs") call-interactively(slime-edit-definition) The only thing that has changed on my side is slime, which I have been updating from CVS. My emacs is 22.2-r2 (gentoo ebuild). Carlos Konstanski

2 5

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 16 Aug '08

16 Aug '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1453 slime/ChangeLog:1.1456 --- slime/ChangeLog:1.1453 Thu Aug 14 11:32:40 2008 +++ slime/ChangeLog Fri Aug 15 18:59:10 2008 @@ -1,3 +1,20 @@ +2008-08-15 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el (slime-popup-buffer-quit): Fix regression; we have to + invoke `bury-buffer' without an argument to make it switch buffers + for us (for the case when the snapshot wasn't restored.) + +2008-08-15 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el (slime-list-compiler-notes): Only shrink if notes tree + isn't displayed as being collapsed. + +2008-08-15 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el (slime-popup-buffer-quit): If not kill, then at least + bury the buffer. + (slime-list-compiler-notes): Shrink the compiler-notes window. + 2008-08-14 Tobias C. Rittweiler <tcr(a)freebits.de> If another frame is already displaying a REPL, `C-c C-z' will now

1 0

[slime-devel] created function echo-area-width
by Greg Pfeil 15 Aug '08

15 Aug '08

I’ve been playing around with having the minibuffer in its own frame that spans the width of my display, but I noticed the slime one-liners were still being truncated to the width of a normal frame. This change uses the width of the minibuffer window that's associated with the current frame (since it is not necessarily the same width as the current frame). Also, I noticed this was a little weird, but haven't looked into it yet. This is what's offered as the arglist for with-open-file on a relatively-recent CCL: (with-open-file (var &key direction element-type if-exists if-does- not-exist external-format class sharing basic) &body body) It seems to be missing the all-important filespec parameter.

2 1

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 13 Aug '08

13 Aug '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1442 slime/ChangeLog:1.1449 --- slime/ChangeLog:1.1442 Mon Aug 11 13:41:59 2008 +++ slime/ChangeLog Tue Aug 12 13:54:43 2008 @@ -1,3 +1,49 @@ +2008-08-12 Helmut Eller <heller(a)common-lisp.net> + + Add a dump-image function to the loader. + + * swank-loader.lisp (dump-image): New. + + * swank-backend.lisp (save-image): New interface. + + * swank-cmucl.lisp, swank-clisp.lisp, swank-sbcl.lisp + (save-image): Implemented. + +2008-08-12 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-repl-send-input): Disable modification hooks + when marking old input. + (slime-check-version): Use y-or-n-p. + +2008-08-12 Helmut Eller <heller(a)common-lisp.net> + + Finally handle reader-errors without disconnecting. + + * swank.lisp (decode-message): Convert reader-error conditions + into :reader-error events. + (dispatch-event): Send :reader-error events to Emacs. + + * slime.el (slime-dispatch-event): Display reader-errors. + +2008-08-12 Helmut Eller <heller(a)common-lisp.net> + + * swank.lisp (with-buffer-syntax): Take package as argument. + (defslimefun): Derive the package for exporting from the symbol. + +2008-08-12 Helmut Eller <heller(a)common-lisp.net> + + Let SIGINT create a synthetic event. + + * swank.lisp (install-fd-handler,simple-serve-requests): Dispatch + a :emacs-interrupt event in the SIGINT handler. + + * slime.el (slime-interrupt): Send nothing over the wire when + SIGINT is used. + +2008-08-11 Helmut Eller <heller(a)common-lisp.net> + + * test.sh: Use batch mode by default. + 2008-08-11 Helmut Eller <heller(a)common-lisp.net> Improve interrupt safety for single-threaded lisps. Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.117 slime/contrib/ChangeLog:1.120 --- slime/contrib/ChangeLog:1.117 Thu Aug 7 11:24:08 2008 +++ slime/contrib/ChangeLog Tue Aug 12 13:54:37 2008 @@ -1,3 +1,17 @@ +2008-08-12 Helmut Eller <heller(a)common-lisp.net> + + * slime-clipboard.el (slime-clipboard-insert-ref): Set + read-nonsticky to t to work better with kill/yank. + * swank-clipboard.lisp (:swank-clipboard): List exports to avoid + compiler warnings. + +2008-08-12 Helmut Eller <heller(a)common-lisp.net> + + Add a simple object clipboard. + + * swank-clipboard.lisp: New file. + * slime-clipboard.el: New file. + 2008-08-07 Tobias C. Rittweiler <tcr(a)freebits.de> * slime-fancy.el: Add slime-mdot-fu and slime-package-fu.

1 0

[slime-devel] Problems starting SLIME
by Stelian Ionescu 12 Aug '08

12 Aug '08

If I save an image containg latest SWANK and try to start SLIME with it, I get an error. OTOH, if I start SLIME with an image that doesn't contain SWANK(loading it on the spot), all works well. I've traced back the origin of this problem to the commit of Sun Aug 3 18:23:10 entitled "Add some flow-control." with CLISP: [1]> ;; Loading file /usr/share/emacs/site-lisp/slime/swank-loader.lisp ... 0 errors, 0 warnings ;; Loaded file /usr/share/emacs/site-lisp/slime/swank-loader.lisp *** - WRITE-CHAR on #<CLOSED IO TERMINAL-STREAM> is illegal The following restarts are available: ABORT :R1 Abort main loop Break 1 [2]> :bt <1/181> #<SYSTEM-FUNCTION SHOW-STACK> 3 <2/174> #<COMPILED-FUNCTION SYSTEM::PRINT-BACKTRACE> <3/168> #<COMPILED-FUNCTION SYSTEM::DEBUG-BACKTRACE> <4/160> #<SYSTEM-FUNCTION SYSTEM::READ-EVAL-PRINT> 2 <5/157> #<COMPILED-FUNCTION SYSTEM::BREAK-LOOP-2-3> <6/153> #<SYSTEM-FUNCTION SYSTEM::SAME-ENV-AS> 2 <7/139> #<COMPILED-FUNCTION SYSTEM::BREAK-LOOP-2> <8/137> #<SYSTEM-FUNCTION SYSTEM::DRIVER> <9/97> #<COMPILED-FUNCTION SYSTEM::BREAK-LOOP> <10/94> #<SYSTEM-FUNCTION INVOKE-DEBUGGER> 1 <11/84> #<SYSTEM-FUNCTION WRITE-STRING> <12/79> #<COMPILED-FUNCTION SWANK::SIMPLE-ANNOUNCE-FUNCTION-1> <13/71> #<COMPILED-FUNCTION SYSTEM::FORMAT-APPLY> <14/66> #<COMPILED-FUNCTION FORMAT> <15/62> #<COMPILED-FUNCTION SWANK::SIMPLE-ANNOUNCE-FUNCTION> <16/60> #<COMPILED-FUNCTION SWANK::ANNOUNCE-SERVER-PORT> <17/57> #<COMPILED-FUNCTION SWANK::START-SERVER-1> <18/51> #<COMPILED-FUNCTION SWANK::SETUP-SERVER> <19/44> #<COMPILED-FUNCTION SWANK:START-SERVER> <20/43> #<SYSTEM-FUNCTION FUNCALL> 4 [39] EVAL frame for form (FUNCALL (READ-FROM-STRING "swank:start-server") "/tmp/.private/hechee/slime.3239193" :CODING-SYSTEM "utf-8-unix") and with SBCL: S/HU[1]> ; loading #P"/usr/share/emacs/site-lisp/slime/swank-loader.lisp" debugger invoked on a SB-SYS:MEMORY-FAULT-ERROR in thread #<THREAD "initial thread" RUNNING {B6209F9}>: Unhandled memory fault at #x-58A13000. Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [ABORT] Exit debugger, returning to top level. (SB-SYS:MEMORY-FAULT-ERROR) 0] backtrace 0: (SB-SYS:MEMORY-FAULT-ERROR) 1: (SB-SYS:MEMORY-FAULT-ERROR)[:EXTERNAL] 2: ("foreign function: #x8063A1C") 3: ("foreign function: #x8063C70") 4: (SB-IMPL::OUTPUT-BYTES/UTF-8 #<SB-SYS:FD-STREAM for "standard error" {9143371}> ";; Swank started at port: " NIL 0 26) 5: (SB-IMPL::FD-SOUT #<SB-SYS:FD-STREAM for "standard error" {9143371}> ";; Swank started at port: " 0 26) 6: (SB-IMPL::%WRITE-STRING ";; Swank started at port: " #<SB-SYS:FD-STREAM for "standard error" {9143371}> 0 26) 7: (WRITE-STRING ";; Swank started at port: " #<SB-SYS:FD-STREAM for "standard error" {9143371}> :START 0 :END NIL) 8: (SB-FORMAT::INTERPRET-DIRECTIVE-LIST #<SB-SYS:FD-STREAM for "standard error" {9143371}> (";; Swank started at port: " #<~D> "." #<~%>) (39770) (39770)) 9: (SB-FORMAT::%FORMAT #<SB-SYS:FD-STREAM for "standard error" {9143371}> "~&;; Swank started at port: ~D.~%" (39770) (39770)) 10: (FORMAT #<SB-SYS:FD-STREAM for "standard error" {9143371}> "~&;; Swank started at port: ~D.~%")[:EXTERNAL] 11: (SWANK::SIMPLE-ANNOUNCE-FUNCTION 39770) 12: (SWANK::ANNOUNCE-SERVER-PORT "/tmp/.private/hechee/slime.3239193" 39770) 13: ((LAMBDA (SWANK::PORT)) 39770) 14: (SWANK::SETUP-SERVER 0 #<CLOSURE (LAMBDA (SWANK::PORT)) {B6F6B75}> :SPAWN NIL :UTF-8) 15: (SWANK:START-SERVER "/tmp/.private/hechee/slime.3239193")[:EXTERNAL] 16: (SB-INT:SIMPLE-EVAL-IN-LEXENV (FUNCALL (READ-FROM-STRING "swank:start-server") "/tmp/.private/hechee/slime.3239193" :CODING-SYSTEM "utf-8-unix") #<NULL-LEXENV>) -- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur.

3 4

[slime-devel] swank-sbcl.lisp:1.213 breaks on windows
by Bart Botta 12 Aug '08

12 Aug '08

Running slime from CVS on sbcl 1.0.19/win32 ends up in the debugger with The variable SB-UNIX:SIGINT is unbound. [Condition of type UNBOUND-VARIABLE] Disabling the (defimplementation install-sigint-handler ...) added in 1.213 with #-win32 seems to fix the problem, no idea if that is the correct solution though. -b-

2 1

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 12 Aug '08

12 Aug '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1428 slime/ChangeLog:1.1442 --- slime/ChangeLog:1.1428 Sat Aug 9 15:57:37 2008 +++ slime/ChangeLog Mon Aug 11 13:41:59 2008 @@ -1,3 +1,69 @@ +2008-08-11 Helmut Eller <heller(a)common-lisp.net> + + Improve interrupt safety for single-threaded lisps. + + * slime.el (slime-interrupt): Send a :emacs-interrupt message + together with SIGINT. SIGINT now means "check for new events" + instead of "invoke the debugger". + + * swank-backend.lisp (install-sigint-handler) + (call-with-user-break-handler): New functions. + + * swank.lisp (simple-serve-requests,install-fd-handler): Use it. + (read-packet): New function. Check for interrupts. + (decode-message): Use it. + (wait-for-event/event-loop): Check for interrupts. + +2008-08-11 Helmut Eller <heller(a)common-lisp.net> + + * swank-abcl.lisp (preferred-communication-style): Return nil + until we implement receive-if. + + * swank-openmcl.lisp (receive-if): Support timeout argument. + * swank-allegro.lisp (receive-if): Ditto. + +2008-08-11 Helmut Eller <heller(a)common-lisp.net> + + * swank.lisp (*global-debugger*): Change default back to t. + +2008-08-10 Helmut Eller <heller(a)common-lisp.net> + + * swank-ecl.lisp (thread-id): Assign an non-nil id to unknown + threads. + + * slime.el (slime-execute-tests): Call slime-test-should-fail-p + before executing the test (which may close the connection). + (def-slime-test): Use slime-sync-to-top-level with a timeout. + (slime-temp-directory): New function. + (slime-run-tests): Save repl-history in /tmp. + (slime-repl-mode): Ignore persistent history if + slime-repl-history-file is nil. + (slime-quit-lisp-internal): New function. + (slime-quit-lisp, slime-restart-inferior-lisp): Use it + (slime-batch-test): Exit, if the Lisp isn't up and running after + 30 secs. + +2008-08-10 Helmut Eller <heller(a)common-lisp.net> + + * swank.lisp (wait-for-event): Add timeout argument. This is used + for :fd-handler and :sigio style where we only process events as + long as we don't block. + (wait-for-event/event-loop, read-event) + (decode-message, receive-if): Ditto. + (process-requests): Renamed from read-from-emacs. + (handle-requests): Renamed from handle-request. Take timeout + argument. Update callers. + (process-available-input): Deleted. + (with-swank-error-handler): Renamed from + with-reader-error-handler. + (with-connection): Use it. + +2008-08-10 Helmut Eller <heller(a)common-lisp.net> + + * swank.lisp (invoke-slime-debugger): New function. + Analagous to cl:invoke-debugger. + (swank-debugger-hook): Use it. + 2008-08-09 Helmut Eller <heller(a)common-lisp.net> * slime.el (slime-quit-lisp): Optionally send kill signal.

1 0

[slime-devel] SLIME warns repeatedly after 1.209
by thom.goodsell＠mac.com 12 Aug '08

12 Aug '08

Something in the changes on the 6th cause slime to freak out on sbcl 1.0.18 w/ threads on OS X. (This is sbcl from macports, if it might make a difference.) cvs update -D '2008-08-06 17:50:37' is the earliest change that reproduces the problem. (The preceding changeset won't start at all; changesets before that work fine.) The symptom is a never-ending chain of these warnings: WARNING: Releasing #S(SB-THREAD:MUTEX :NAME NIL :%OWNER NIL :LUTEX #<unknown pointer object, widetag=#x5E {11D7111F}>), owned by another thread: NIL I haven't tried to track down the problem, yet. Does anything seem obvious to those responsible for the relevant changes? Thanks, Thom

3 2

[slime-devel] new debugger behavior?
by Carlos Konstanski 11 Aug '08

11 Aug '08

Last week I upgraded from slime-2.0_p20070816 to slime-2.0_p20080731 (these are the gentoo ebuild names). We're looking at a pretty big jump here; these builds are a year apart. In that year, something changed in the debugger that is not to my liking. I am hoping that it is a feature that I can turn off. When I hit an error in my code, I no longer enter the debugger. Instead, I just get a printed backtrace in the REPL. If I put a (break) in the code, I do enter the debugger. I would like to enter the debugger on all errors, like the good old days. Does this sound like a feature that was added in the last year? Or do I need to look elsewhere for the cause? Carlos Konstanski

4 13

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel August 2008