January 2008 - slime-devel - mailman3.common-lisp.net

[slime-devel] Saving *slime-scratch*
by Nikodemus Siivola 11 Oct '08

11 Oct '08

The attached patch associates *slime-scratch* with a file if you name one as "slime-scratch-file". I've been running slime with this a while, and rather like it. Something like this was talked about a while ago, and dropped because of what looked like an ideologinal objection to scratch-buffers in my mind. Is the consensus still against this? Cheers, -- Nikodemus Index: slime.el =================================================================== RCS file: /project/slime/cvsroot/slime/slime.el,v retrieving revision 1.784 diff -u -r1.784 slime.el --- slime.el 16 Apr 2007 14:42:33 -0000 1.784 +++ slime.el 27 Apr 2007 13:26:17 -0000 @@ -4570,10 +4570,15 @@ (set-keymap-parent map lisp-mode-map) map)) +(defvar slime-scratch-file nil) + (defun slime-scratch-buffer () "Return the scratch buffer, create it if necessary." (or (get-buffer "*slime-scratch*") - (with-current-buffer (get-buffer-create "*slime-scratch*") + (with-current-buffer (if (not slime-scratch-file) + (get-buffer-create "*slime-scratch*") + (find-file slime-scratch-file)) + (rename-buffer "*slime-scratch*") (lisp-mode) (use-local-map slime-scratch-mode-map) (slime-mode t)

4 5

[slime-devel] fancy inspector problems
by Knut Olav Bøhmer 18 Jun '08

18 Jun '08

When I inspect the object from lispworks it works ------------------ CL-USER> (inspect <http://www.lispworks.com/reference/HyperSpec/Body/f_inspec.htm> k2::*current-hushe* ) #<HUSHE-CLIENT:HUSHE-CLIENT 118742AB> is a HUSHE-CLIENT:HUSHE-CLIENT TIMESTAMP 3398596745 TIMEOUT 1200 I/O-PACKAGE #<The HUSHE-CLIENT package, 135/256 internal, 101/256 external> LOCK #<MP:LOCK "Hushe-client serializer" Unlocked NIL 0 118742DF> TCPCLIENT-STREAM #<COMM:SOCKET-STREAM 11875E87> HOST "localhost" PORT 11116 ERROR-FORMAT "GENERIC-TCP-CLIENT ERROR: ~a" ---------------- But when I inspect with slime I get this: (note I use all contib mocules, and <http://www.lispworks.com/reference/HyperSpec/Body/a_and.htm> it is latest cvs) ---------------------- The slot #<STANDARD-EFFECTIVE-SLOT-DEFINITION GENERIC-TCPCLIENT::ERROR-FORMAT 1121052F> is missing from #<HUSHE-CLIENT:HUSHE-CLIENT 11A11963> (of class <http://www.lispworks.com/reference/HyperSpec/Body/t_class.htm> #<STANDARD-CLASS <http://www.lispworks.com/reference/HyperSpec/Body/t_std_cl.htm> HUSHE-CLIENT:HUSHE-CLIENT 10A27AEB>), when reading the value. [Condition of type CONDITIONS::SLOT-MISSING-ERROR] Restarts: 0: [ABORT] Return to SLIME's top level. 1: [ABORT] Quit process. Backtrace: 0: CONDITIONS::CONDITIONS-ERROR (:INVISIBLEP T <http://www.lispworks.com/reference/HyperSpec/Body/a_t.htm> CONDITIONS::SLOT-MISSING-ERROR (:NAME #<STANDARD-EFFECTIVE-SLOT-DEFINITION GENERIC-TCPCLIENT::ERROR-FORMAT 1121052F> :INSTANCE #<HUSHE-CLIENT:HUSHE-CLIENT 11A11963> :CLASS #<STANDARD-CLASS <http://www.lispworks.com/reference/HyperSpec/Body/t_std_cl.htm> HUSHE-CLIENT:HUSHE-CLIENT 10A27AEB> :OPERATION ..)) 1: ERROR (CONDITIONS::SLOT-MISSING-ERROR &REST (:NAME #<STANDARD-EFFECTIVE-SLOT-DEFINITION GENERIC-TCPCLIENT::ERROR-FORMAT 1121052F> :INSTANCE #<HUSHE-CLIENT:HUSHE-CLIENT 11A11963> :CLASS #<STANDARD-CLASS <http://www.lispworks.com/reference/HyperSpec/Body/t_std_cl.htm> HUSHE-CLIENT:HUSHE-CLIENT 10A27AEB> :OPERATION SLOT-BOUNDP <http://www.lispworks.com/reference/HyperSpec/Body/f_slt_bo.htm> ..)) 2: (METHOD <http://www.lispworks.com/reference/HyperSpec/Body/t_method.htm> SLOT-MISSING <http://www.lispworks.com/reference/HyperSpec/Body/f_slt_mi.htm> (T <http://www.lispworks.com/reference/HyperSpec/Body/a_t.htm> T <http://www.lispworks.com/reference/HyperSpec/Body/a_t.htm> T <http://www.lispworks.com/reference/HyperSpec/Body/a_t.htm> T <http://www.lispworks.com/reference/HyperSpec/Body/a_t.htm>)) (#<STANDARD-CLASS <http://www.lispworks.com/reference/HyperSpec/Body/t_std_cl.htm> HUSHE-CLIENT:HUSHE-CLIENT 10A27AEB> #<HUSHE-CLIENT:HUSHE-CLIENT 11A11963> #<STANDARD-EFFECTIVE-SLOT-DEFINITION GENERIC-TCPCLIENT::ERROR-FORMAT 1121052F> SLOT-BOUNDP <http://www.lispworks.com/reference/HyperSpec/Body/f_slt_bo.htm> &OPTIONAL NIL <http://www.lispworks.com/reference/HyperSpec/Body/a_nil.htm>) 3: CLOS::GENERIC-FUNCTION-NON-DISCRIMINATOR NIL 4: CLOS::SLOT-BOUNDP-MISSING (#(1571 (GENERIC-TCPCLIENT::TCPCLIENT-STREAM GENERIC-TCPCLIENT::HOST GENERIC-TCPCLIENT::PORT GENERIC-TCPCLIENT::TIMEOUT GENERIC-TCPCLIENT::I/O-PACKAGE GENERIC-TCPCLIENT::ERROR-FORMAT HUSHE-CLIENT::TIMESTAMP HUSHE-CLIENT::LOCK) NIL <http://www.lispworks.com/reference/HyperSpec/Body/a_nil.htm> ..)) 5: (METHOD <http://www.lispworks.com/reference/HyperSpec/Body/t_method.htm> SWANK:INSPECT-SLOT-FOR-EMACS (T <http://www.lispworks.com/reference/HyperSpec/Body/a_t.htm> T <http://www.lispworks.com/reference/HyperSpec/Body/a_t.htm> T <http://www.lispworks.com/reference/HyperSpec/Body/a_t.htm>)) (#<STANDARD-CLASS <http://www.lispworks.com/reference/HyperSpec/Body/t_std_cl.htm> HUSHE-CLIENT:HUSHE-CLIENT 10A27AEB> #<HUSHE-CLIENT:HUSHE-CLIENT 11A11963> #<STANDARD-EFFECTIVE-SLOT-DEFINITION GENERIC-TCPCLIENT::ERROR-FORMAT 1121052F>) 6: (SUBFUNCTION 1 (METHOD <http://www.lispworks.com/reference/HyperSpec/Body/t_method.htm> CLOS::UPDATE-DISCRIMINATOR-CODE (STANDARD-GENERIC-FUNCTION <http://www.lispworks.com/reference/HyperSpec/Body/t_std_ge.htm>))) (:INVISIBLEP T <http://www.lispworks.com/reference/HyperSpec/Body/a_t.htm> &REST (#<STANDARD-CLASS <http://www.lispworks.com/reference/HyperSpec/Body/t_std_cl.htm> HUSHE-CLIENT:HUSHE-CLIENT 10A27AEB> #<HUSHE-CLIENT:HUSHE-CLIENT 11A11963> #<STANDARD-EFFECTIVE-SLOT-DEFINITION GENERIC-TCPCLIENT::ERROR-FORMAT 1121052F>)) 7: (METHOD <http://www.lispworks.com/reference/HyperSpec/Body/t_method.htm> SWANK::ALL-SLOTS-FOR-INSPECTOR (STANDARD-OBJECT <http://www.lispworks.com/reference/HyperSpec/Body/t_std_ob.htm> T <http://www.lispworks.com/reference/HyperSpec/Body/a_t.htm>)) (#<HUSHE-CLIENT:HUSHE-CLIENT 11A11963> :DONT-KNOW) 8: CLOS::CACHE-MISS-FUNCTION (:INVISIBLEP T <http://www.lispworks.com/reference/HyperSpec/Body/a_t.htm> &REST (#<HUSHE-CLIENT:HUSHE-CLIENT 11A11963> #<SWANK::FANCY-INSPECTOR 1188D817>)) 9: (SUBFUNCTION 1 (METHOD <http://www.lispworks.com/reference/HyperSpec/Body/t_method.htm> CLOS::UPDATE-DISCRIMINATOR-CODE (STANDARD-GENERIC-FUNCTION <http://www.lispworks.com/reference/HyperSpec/Body/t_std_ge.htm>))) (:INVISIBLEP T <http://www.lispworks.com/reference/HyperSpec/Body/a_t.htm> &REST (#<HUSHE-CLIENT:HUSHE-CLIENT 11A11963> #<SWANK::FANCY-INSPECTOR 1188D817>)) 10: (METHOD <http://www.lispworks.com/reference/HyperSpec/Body/t_method.htm> SWANK-BACKEND:INSPECT-FOR-EMACS (STANDARD-OBJECT <http://www.lispworks.com/reference/HyperSpec/Body/t_std_ob.htm> SWANK::FANCY-INSPECTOR)) (#<HUSHE-CLIENT:HUSHE-CLIENT 11A11963> #<SWANK::FANCY-INSPECTOR 1188D817>) 11: CLOS::CACHE-MISS-FUNCTION (:INVISIBLEP T <http://www.lispworks.com/reference/HyperSpec/Body/a_t.htm> &REST (#<HUSHE-CLIENT:HUSHE-CLIENT 11A11963> #<SWANK::FANCY-INSPECTOR 1188D817>)) 12: (SUBFUNCTION 1 (METHOD <http://www.lispworks.com/reference/HyperSpec/Body/t_method.htm> CLOS::UPDATE-DISCRIMINATOR-CODE (STANDARD-GENERIC-FUNCTION <http://www.lispworks.com/reference/HyperSpec/Body/t_std_ge.htm>))) (:INVISIBLEP T <http://www.lispworks.com/reference/HyperSpec/Body/a_t.htm> &REST (#<HUSHE-CLIENT:HUSHE-CLIENT 11A11963> #<SWANK::FANCY-INSPECTOR 1188D817>)) 13: SWANK::INSPECT-OBJECT (#<HUSHE-CLIENT:HUSHE-CLIENT 11A11963> &OPTIONAL "<(INSPECTOR *DEFAULT-INSPECTOR*)>") 14: (SUBFUNCTION 1 SWANK:INIT-INSPECTOR) NIL 15: SWANK-BACKEND:CALL-WITH-SYNTAX-HOOKS (#<Closure 1 subfunction of SWANK:INIT-INSPECTOR>) 16: SWANK::CALL-WITH-BUFFER-SYNTAX (#<Closure 1 subfunction of SWANK:INIT-INSPECTOR>) 17: SYSTEM::%INVOKE (:INVISIBLEP T <http://www.lispworks.com/reference/HyperSpec/Body/a_t.htm>) 18: SYSTEM::%EVAL ((SWANK:INIT-INSPECTOR "k2::*current-hushe*")) 19: EVAL ((SWANK:INIT-INSPECTOR "k2::*current-hushe*")) 20: (SUBFUNCTION 1 SWANK::EVAL-FOR-EMACS) NIL 21: (SUBFUNCTION 1 (TOP-LEVEL-FORM 52)) (#</Function/ <http://www.lispworks.com/reference/HyperSpec/Body/a_fn.htm> SWANK:SWANK-DEBUGGER-HOOK> #<Closure 1 subfunction of SWANK::EVAL-FOR-EMACS>) 22: SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK (#</Function/ <http://www.lispworks.com/reference/HyperSpec/Body/a_fn.htm> SWANK:SWANK-DEBUGGER-HOOK> #<Closure 1 subfunction of SWANK::EVAL-FOR-EMACS>) 23: FUNCALL (SWANK::EVAL-FOR-EMACS &REST ((SWANK:INIT-INSPECTOR "k2::*current-hushe*") "COMMON-LISP-USER" 13)) 24: SWANK::READ-FROM-EMACS NIL 25: (SUBFUNCTION 1 SWANK::HANDLE-REQUEST) NIL 26: (SUBFUNCTION 1 (TOP-LEVEL-FORM 52)) (#</Function/ <http://www.lispworks.com/reference/HyperSpec/Body/a_fn.htm> SWANK:SWANK-DEBUGGER-HOOK> #</Function/ <http://www.lispworks.com/reference/HyperSpec/Body/a_fn.htm> 1 subfunction of SWANK::HANDLE-REQUEST>) 27: SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK (#</Function/ <http://www.lispworks.com/reference/HyperSpec/Body/a_fn.htm> SWANK:SWANK-DEBUGGER-HOOK> #</Function/ <http://www.lispworks.com/reference/HyperSpec/Body/a_fn.htm> 1 subfunction of SWANK::HANDLE-REQUEST>) 28: (SUBFUNCTION 1 SWANK::CALL-WITH-CONNECTION) NIL 29: SWANK::CALL-WITH-REDIRECTED-IO (#<SWANK::CONNECTION 1192C3E7> #<Closure 1 subfunction of SWANK::CALL-WITH-CONNECTION>) 30: SWANK::CALL-WITH-CONNECTION (#<SWANK::CONNECTION 1192C3E7> #</Function/ <http://www.lispworks.com/reference/HyperSpec/Body/a_fn.htm> 1 subfunction of SWANK::HANDLE-REQUEST>) 31: SWANK::HANDLE-REQUEST (#<SWANK::CONNECTION 1192C3E7>) 32: SWANK::REPL-LOOP (#<SWANK::CONNECTION 1192C3E7>) 33: (SUBFUNCTION 1 SWANK::SPAWN-REPL-THREAD) NIL 34: SWANK::CALL-WITH-BINDINGS (NIL <http://www.lispworks.com/reference/HyperSpec/Body/a_nil.htm> #<Closure 1 subfunction of SWANK::SPAWN-REPL-THREAD>) 35: (SUBFUNCTION 1 SWANK::SPAWN-REPL-THREAD) NIL 36: (SUBFUNCTION MP::PROCESS-SG-FUNCTION MP::INITIALIZE-PROCESS-STACK) (:DONT-KNOW) 37: SYSTEM::%%FIRST-CALL-TO-STACK NIL 38: SYSTEM::%%FIRST-CALL-TO-STACK NIL -- Free Software Consultant Cell: +47 - 47 34 40 08 Phone: +47 - 21 53 69 00, Fax: +47 - 21 53 69 09 Addr: Slemdalsveien 70, PB 1 Vinderen, 0319 Oslo <http://www.freecode.no/>

4 11

[slime-devel] Patch for ABCL GETPID implementation
by Mark Evenson 22 Feb '08

22 Feb '08

Apparently PPID for the parent process id is not a standard feature of the Bourne shell (or at least it isn't present under solaris-5.11). Attached is a patch to my ABCL GETPID implementation that uses HANDLER-CASE to return '0' if any error is raised in attempting to getpid(). -- <Mark.Evenson(a)gmx.at> "[T]his is not a disentanglement from, but a progressive knotting into." diff -r 0c36088c65c0 swank-abcl.lisp --- a/swank-abcl.lisp Wed Jan 02 17:02:52 2008 +0100 +++ b/swank-abcl.lisp Wed Jan 23 12:09:39 2008 +0100 @@ -143,8 +143,7 @@ (funcall fn)) (defimplementation getpid () - (if (not (find :unix *features*)) - 0 + (handler-case (let* ((runtime (java:jstatic "getRuntime" "java.lang.Runtime")) (command @@ -153,8 +152,8 @@ (runtime-exec-jmethod ;; Complicated because java.lang.Runtime.exec() is ;; overloaded on a non-primitive type (array of - ;; java.lang.String), so we have to use the actual parameter - ;; instance to get java.lang.Class + ;; java.lang.String), so we have to use the actual + ;; parameter instance to get java.lang.Class (java:jmethod "java.lang.Runtime" "exec" (java:jcall (java:jmethod "java.lang.Object" "getClass") @@ -162,19 +161,19 @@ (process (java:jcall runtime-exec-jmethod runtime command)) (output - (java:jcall (java:jmethod "java.lang.Process" "getInputStream") + (java:jcall (java:jmethod "java.lang.Process" "getInputStream") process))) - (java:jcall (java:jmethod "java.lang.Process" "waitFor") process) - (loop - :with b - :do (setq b - (java:jcall (java:jmethod "java.io.InputStream" "read") - output)) - :until (member b '(-1 #x0a)) ; Either EOF or LF - :collecting (code-char b) :into result - :finally (return - (values - (parse-integer (coerce result 'string)))))))) + (java:jcall (java:jmethod "java.lang.Process" "waitFor") + process) + (loop :with b :do + (setq b + (java:jcall (java:jmethod "java.io.InputStream" "read") + output)) + :until (member b '(-1 #x0a)) ; Either EOF or LF + :collecting (code-char b) :into result + :finally (return + (parse-integer (coerce result 'string))))) + (t () 0))) (defimplementation lisp-implementation-type-name () "armedbear")

2 3

[slime-devel] Re: Expand imported symbol with package name
by Numeromancer 07 Feb '08

07 Feb '08

Tobias C. Rittweiler wrote: > > Numeromancer <tschaef(a)sbcglobal.net> writes: > > >> >> Does slime have a function which will qualify the symbol at point with >> >> its package name if it is imported? And the obvious extension, >> >> qualifying all symbols in the region or file? Does anyone have any >> >> hints on how one might create such a function? > > > > What do you mean with "if it is imported"? Do you really only mean if > > the symbol was imported via IMPORT or via the :IMPORT-FROM clause of > > DEFPACKAGE? What do you want this for? > > > > -T. > > Sorry about the delay. Perhaps "imported" is not technically correct. "Available in the current package without qualification" might be better. Or not. I mean this: if I am in package foo, which uses cl, for example, then (map 'func-in-foo (list 1 2 3 var-in-foo)) would be transformed to (cl:map 'func-in-foo (cl:list 1 2 3 var-in-foo)) if the whole expression were in the region. The symbols in the current package are not qualified. Or, the package name is an argument and only symbols in that package are so qualified. This would help in finding details of the dependencies between packages. E.g.: If I have a utils package (don't we all?) and another package, foo maybe, and I want to split the latter off into a separate project, I may want to see if I can easily make it independent of utils. Macroexpanding will show me this, but if Slime could do as I suggest I could change the buffer and then one-by-one change the use of objects in util to something else, and thereby remove any dependency on the util package. Or, similarly, I might want to continue to use utils in foo but not :use it, and so force all symbols from utils to have package qualifiers. I could then :use instead some new package that has symbols which conflict with symbols in utils. I hope this is clear. These are not everyday tasks, but they can be tedious, and what I have suggested would help. Thanks Tim S

2 2

[slime-devel] Missing features in latest CVS
by Maciej Katafiasz 06 Feb '08

06 Feb '08

Hi, I recently upgraded from 2007-05-24 to 2007-11-16 snapshot, and I notice there are some useful features that are now gone. I've tried enabling basically everything in contrib/, but those two I can't get back: - Inspecting a (plain) function object now only shows its name and docstring. It used to show much more, in particular recorded debug information, source file and disassembled compiled code - There are no presentations in SLDB backtraces. I find presentations immensely useful for inspecting backtraces, and I miss them a lot. I do get presentations everywhere else, including streams, but not in the debugger I'm using SBCL 1.0.10 on x86/Linux, and SBCL hasn't changed since I used the May snapshot. Cheers, Maciej

6 12

[slime-devel] Automatic shrinking of windows (slime-documentation, etc)?
by Ivar Refsdal 01 Feb '08

01 Feb '08

Hello all. Thanks for a nice lisp development environment! I have a simple question. Is it possible to run (shrink-window-if-larger-than-buffer) when running such commands as slime-documentation? Could this feature or option perhaps be added to Slime? I've tried with defadvice, but no luck yet. At the moment I've simply inserted a shrink-window-if.. call into the macro slime-with-output-to-temp-buffer. That works, however that macro is used by a bunch of other things, so it might (or will) break other things. Thanks in advance, -Ivar Refsdal

2 1

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

28 Jan '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1272 slime/ChangeLog:1.1274 --- slime/ChangeLog:1.1272 Mon Jan 21 06:51:07 2008 +++ slime/ChangeLog Sun Jan 27 10:34:27 2008 @@ -1,3 +1,21 @@ +2008-01-27 Helmut Eller <heller(a)common-lisp.net> + + Make it easier to start a non-default Lisp from ELisp code. + + * slime.el (slime): If the argument is a symbol start the + corresponding entry in slime-lisp-implementations. + Typical use is something like: + (defun cmucl () (interactive) (slime 'cmucl)) + +2008-01-22 Luís Oliveira <loliveira(a)common-lisp.net> + + * swank-source-path-parser.lisp (make-source-recording-readtable): + don't suppress the #. reader macro. + (read-and-record-source-map): don't bind *read-eval* to nil. + (suppress-sharp-dot): unused, delete it. + + * slime.el (test compile-defun): test with #+#.'(:and). + 2008-01-21 Helmut Eller <heller(a)common-lisp.net> * slime.el (sldb-mode): Don't throw to toplevel in the Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.80 slime/contrib/ChangeLog:1.82 --- slime/contrib/ChangeLog:1.80 Sun Jan 20 11:18:49 2008 +++ slime/contrib/ChangeLog Sun Jan 27 05:17:34 2008 @@ -1,3 +1,21 @@ +2008-01-27 Helmut Eller <heller(a)common-lisp.net> + + Make autodoc use the correct width of the typeout-window. + + * slime-autodoc.el (slime-autodoc-dimensions-function): New + variable. + (slime-autodoc-message-dimensions): Use it. + + * slime-typeout-frame.el (slime-typeout-autodoc-dimensions): New + function. + (slime-typeout-frame-init): Use it. + +2008-01-27 Helmut Eller <heller(a)common-lisp.net> + + Use slime-require instead of a connected-hook. + + * slime-autodoc.el (slime-autodoc-on-connect): Deleted. + 2008-01-20 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> Hook presentations into debugger and inspector, restoring

1 0

[slime-devel] Problem loading OpenMCL
by Chris Van Dusen 27 Jan '08

27 Jan '08

Hi, I've been running Emacs/Slime/OpenMCL on Mac OS X Tiger (PPC) for several months now with no problem. I just updated and rebuilt OpenMCL (via (ccl:rebuild-ccl :force t)), and now when starting slime, I get the following error. I then updated Slime with the current CVS, but am still getting the error. Does anyone have an idea as to what is going wrong? Thanks, Chris Van Dusen. (progn (load "/Users/chrisvandusen/bin/slime/slime/swank- loader.lisp" :verbose t) (funcall (read-from-string "swank:start- server") "/tmp/slime.521" :coding-system "iso-latin-1-unix")) ; loading system definition from /Users/chrisvandusen/.asdf-install- dir/systems/asdf-install.asd into #<Package "ASDF0"> ; registering #<SYSTEM ASDF-INSTALL #x85B21D6> as ASDF-INSTALL Welcome to OpenMCL Version 1.1-r7706 (DarwinPPC32)! ? ;Loading #P"/Users/chrisvandusen/bin/slime/slime/swank-loader.lisp"... ;Compiling "/Users/chrisvandusen/bin/slime/slime/swank-backend.lisp"... ;Loading #P"/Users/chrisvandusen/.slime/fasl/2007-11-23/openmcl-1.1- darwin-powerpc/swank-backend.dfsl"... ;Compiling "/Users/chrisvandusen/bin/slime/slime/nregex.lisp"... ;Loading #P"/Users/chrisvandusen/.slime/fasl/2007-11-23/openmcl-1.1- darwin-powerpc/nregex.dfsl"... ;Compiling "/Users/chrisvandusen/bin/slime/slime/metering.lisp"... ;Loading #P"/Users/chrisvandusen/.slime/fasl/2007-11-23/openmcl-1.1- darwin-powerpc/metering.dfsl"... ;Compiling "/Users/chrisvandusen/bin/slime/slime/swank-openmcl.lisp"... ;Loading #P"/Users/chrisvandusen/.slime/fasl/2007-11-23/openmcl-1.1- darwin-powerpc/swank-openmcl.dfsl"... ;Compiling "/Users/chrisvandusen/bin/slime/slime/swank-gray.lisp"... ;Loading #P"/Users/chrisvandusen/.slime/fasl/2007-11-23/openmcl-1.1- darwin-powerpc/swank-gray.dfsl"... ;Compiling "/Users/chrisvandusen/bin/slime/slime/swank.lisp"... ;Loading #P"/Users/chrisvandusen/.slime/fasl/2007-11-23/openmcl-1.1- darwin-powerpc/swank.dfsl"...;; ;; Error while loading: /Users/ chrisvandusen/.slime/fasl/2007-11-23/openmcl-1.1-darwin-powerpc/ swank.dfsl ;; Condition: Package name "SWANK-IO- PACKAGE" is already in use. ;; Aborting. ;; ?

3 3

[slime-devel] [BUG] slime-autodoc uses wrong line width with slime-typeout-frame
by Michael Weber 27 Jan '08

27 Jan '08

Test case: With slime-autodoc and slime-typeout-frame set up: (setq slime-autodoc-use-multiline-p t) M-x slime-ensure-typeout-frame enlarge the frame with the lisp buffer frame to be wider than the typeout frame; move cursor inside some form with large autodoc string (e.g., w-o-t-s); The autodoc string shows up in the typeout buffer, but with line breaks according to the width of the lisp buffer, IOW, lines are too partly obscured. Cheers, Michael

2 1

[slime-devel] #+#. bug report (with fix, maybe)
by Luis Oliveira 27 Jan '08

27 Jan '08

Hello, While trying to compile some code that contained the #+#. idiom I came across a bug in SLIME. Here's a minimal test case: (defun foo () #+#.'(:and) (/ 1 0)) And some variations: (defun foo () #+#.'(:and) t (/ 1 0)) (defun foo () (let (unused) #+#.'(:and) t)) Trying to compile these examples through, e.g., slime-compile-file or slime-compile-defun results in a cryptic error: unknown operator in feature expression: (#:|#.1|). [Condition of type SIMPLE-ERROR] What these three examples have in common is that a compiler note is generated and the offending form contains #+#. which makes SWANK-BACKEND::LOCATE-COMPILER-NOTE choke. What happens is that READ-AND-RECORD-SOURCE-MAP overrides #. and makes it return a gensym, #:|#.1| in this particular example, which is then passed to #+ and causes the error above. SUPPRESS-SHARP-DOT sets things up so that #. returns a gensym instead of NIL in order to "avoid multiple entries for nil at toplevel in the source-map", according to the ChangeLog. Even if we ignore that problem, having #. return NIL in this case, while it would dodge the error, it wouldn't find or properly annotate the offending (/ 1 0) form since #+cl:nil usually suppresses forms. The attached patch gets rid of SUPPRESS-SHARP-DOT. That not only fixes my original problem but also makes the following example work better than it before, since the (/ 1 0) form is now annotated: #.'(defun foo () (/ 1 0)) I believe that was the case the ChangeLog entry I quoted was referring to. However, I have the feeling that there might be some good reason why #. was suppressed in the first place. Any ideas? (BTW, it took me a while to figure out this bug was coming from within SLIME itself, and it might have taken even longer if someone hadn't noticed that compiling the software in question without SLIME worked without problem. Perhaps it would be helpful to somehow report internal errors as such?) -- Luís Oliveira http://student.dei.uc.pt/~lmoliv/

2 1