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

[OSX/CMU-CL] Problems with inspector
by Didier Verna 29 Jan '18

29 Jan '18

Hello, while trying to inspect values from Slime in a session with CMUCL 21c, I get the following error. I'm on OSX with CMUCL 21.c from the binary darwin-x86 tarballs. Thanks! Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER:Error (TYPE-ERROR) during printing: #<TYPE-ERROR {49F0548D}> [Condition of type TYPE-ERROR] Restarts: 0: [RETRY] Retry SLIME inspection request. 1: [*ABORT] Return to SLIME's top level. 2: [ABORT] Return to Top-Level. Backtrace: 0: (SWANK/CMUCL::MAILBOX NIL)Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER: NIL is not of type MULTIPROCESSING::PROCESS 1: ((FLET SWANK/BACKEND:SEND) NIL T)Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER: NIL is not of type MULTIPROCESSING::PROCESS 2: ("DEFMETHOD STREAM-WRITE-STRING (SLIME-OUTPUT-STREAM T)")Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER: NIL is not of type MULTIPROCESSING::PROCESS 3: ((METHOD STREAM-WRITE-STRING NIL (SWANK/GRAY::SLIME-OUTPUT-STREAM T)) (#(2 1 3 4 0) . #(#)) #<unused-arg> #<SWANK/GRAY::SLIME-OUTPUT-STREAM {49EFAD3D}> "#<" ...)Type-error in KERNEL::OBJECT-NOT-TYPE-E.. 4: (LISP::WRITE-STRING* "#<" #<SWANK/GRAY::SLIME-OUTPUT-STREAM {49EFAD3D}> 0 2)Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER: NIL is not of type MULTIPROCESSING::PROCESS 5: (LISP::%PRINT-UNREADABLE-OBJECT #<Method-Combination OR (:MOST-SPECIFIC-FIRST) {49ED7BB5}> #<SWANK/GRAY::SLIME-OUTPUT-STREAM {49EFAD3D}> T T ...)Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER: N.. 6: (SWANK::CALL/TRUNCATED-OUTPUT-TO-STRING 200 #<Closure Over Function "DEFUN PREPARE-TITLE" {49EFAB59}> "..")Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER: NIL is not of type MULTIPROCESSING::PRO.. 7: (SWANK::CALL-WITH-BINDINGS ((*PRINT-LINES* . 1) (*PRINT-RIGHT-MARGIN* . 75) (*PRINT-PRETTY* . T) (*PRINT-READABLY*)) #<Closure Over Function "DEFUN PREPARE-TITLE" {49EFAAD9}>)Type-error in KERNEL::OBJ.. 8: (SWANK::ISTATE>ELISP #S(SWANK::ISTATE :OBJECT #<Method-Combination OR # {49ED7BB5}> :VERBOSE NIL :PARTS #() :ACTIONS #() :METADATA-PLIST (:SORT-ORDER # :GROUPING-KIND # :CHECKLIST ...) ...))Type-error.. 9: (SWANK::CALL-WITH-RETRY-RESTART "Retry SLIME inspection request." #<Closure Over Function "DEFSLIMEFUN INIT-INSPECTOR" {49EEAFA9}>)Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER: NIL is not of t.. 10: (SWANK::CALL-WITH-BUFFER-SYNTAX NIL #<Closure Over Function "DEFSLIMEFUN INIT-INSPECTOR" {49EEAF99}>)Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER: NIL is not of type MULTIPROCESSING::PROCESS 11: (SWANK:EVAL-FOR-EMACS (SWANK:INIT-INSPECTOR "*") "COMMON-LISP-USER" 50)Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER: NIL is not of type MULTIPROCESSING::PROCESS 12: (SWANK::PROCESS-REQUESTS T)Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER: NIL is not of type MULTIPROCESSING::PROCESS 13: ("DEFUN HANDLE-REQUESTS")Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER: NIL is not of type MULTIPROCESSING::PROCESS 14: ("DEFUN HANDLE-REQUESTS")Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER: NIL is not of type MULTIPROCESSING::PROCESS 15: ("DEFINTERFACE CALL-WITH-DEBUGGER-HOOK" #<Function SWANK:SWANK-DEBUGGER-HOOK {48107A89}> #<Closure Over Function "DEFUN HANDLE-REQUESTS" {49EE99E1}>)Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER.. 16: (SWANK::CALL-WITH-BINDINGS ((*STANDARD-INPUT* . #) (*STANDARD-OUTPUT* . #) (*TRACE-OUTPUT* . #) (*ERROR-OUTPUT* . #) (*DEBUG-IO* . #<Two-Way Stream, Input = #, Output = #>) ...)Type-error in KERNEL::O.. 17: (SWANK::HANDLE-REQUESTS #<SWANK::SINGLETHREADED-CONNECTION {49D65FFD}> T)Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER: NIL is not of type MULTIPROCESSING::PROCESS 18: (SWANK::INVOKE-OR-QUEUE-INTERRUPT #<Closure Over Function "DEFUN PROCESS-IO-INTERRUPT" {49EE93B1}>)Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER: NIL is not of type MULTIPROCESSING::PROCESS 19: (SWANK::PROCESS-IO-INTERRUPT #<SWANK::SINGLETHREADED-CONNECTION {49D65FFD}>)Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER: NIL is not of type MULTIPROCESSING::PROCESS -- Resistance is futile. You will be jazzimilated. Lisp, Jazz, Aïkido: http://www.didierverna.info

3 8

ACL MacOS 10.1 SLIME Inspect bug with SLIME 2.20
by Mark H. David 27 Jan '18

27 Jan '18

The SLIME inspect feature within SLIME in 2.20 does not work with ACL in our testing on version 10.1 on MacOS with "alisp" images, both SMP and non-SMP. The same SLIME inspect feature does work in the previous version, SLIME 2.19. Finally, there's no known problem with SLIME inspect with any other Lisps that we've tried in either of the versions of SLIME (2.19, 2.20), i.e., with CCL and SBCL. To recreate, launch SLIME of the appropriate version (2.20) with the appropriate inferior Lisp (ACL alisp 10.1/MacOS), then run slime inspect on any object. For example, do M-x slime-inspect [ret] () [ret] The above invokes SLIME inspect to inspect the Lisp object nil, entered as (). One could use any Lisp object, e.g., the list '(1 2 3). So, the above command ought to put you in a SLIME inspect buffer to let you inspect the object. Instead, it throws you into a debugger buffer. Then, in addition, it is particularly onerous because the input prompted for by the debugger is not apparently responded to. For example, typing q to quit or 3 to abort does nothing. You apparently can do nothing but manually kill the emacs buffers involved with Lisp/SLIME. See an attached screen shot for a picture of how the debugger buffer looks. The screen shot shows that the debugger is somewhere in no-applicable-method MULTIPROCESSING:PROCESS-PROPERTY-LIST.

2 2

best way to report slime bug reports/issues
by Mark H. David 26 Jan '18

26 Jan '18

Is this list the best way to report bugs and issues with SLIME for everyday users? Is the github repo a better place? Is there some other list? Thanks, Mark

2 1

how to control version of slime in emacs (using melpa package installer)
by Mark H. David 24 Jan '18

24 Jan '18

Hi, I installed SLIME with the package installer (melpa), and I have no idea how to control the version. I would like to run version 2.20, but I seem to have version 2.19. Does anyone know how I can change to version 2.20? I cannot find any documentation about this. Can anyone point this out? Thanks, Mark

3 2

Using ANSI colors?
by Ben Lambert 07 Jan '18

07 Jan '18

Hi there, I just posted an "Issue" on GitHub (https://github.com/slime/slime/issues/420 <https://github.com/slime/slime/issues/420>), and then saw in the README that questions are better directed to this list. I'm not sure how to search the email archives so I'm not sure if this has been asked before. The question (repeated from GitHub) is: I've wondered about this for a while. Is it possible to print with ANSI colors in a Slime repl buffer? If I load the cl-ansi-text library from Quicklisp (ql:quickload :cl-ansi-text), and I run (cl-ansi-text:yellow "yellow") in the Slime REPL the output is: "[33myellow[0m". When I run the same commands directly in an SBCL REPL, it prints as expected "yellow" in a yellow color. Is it possible to use ANSI colors in Slime? Or maybe there's some workaround? Thanks, Ben

2 4

finding an implementation of SWANK interface
by 73budden . 06 Jan '18

06 Jan '18

Hi! Maybe I'm missing something, but I don't know how do I find defimplementation of some definterface. E.g. I want to go to swank/backend:activate-stepping, but EMACS only sends me to definterface, and I have to grep for defimplementation. I don't know how should I handle this, but I added a simple defparameter into defimplementation form. Now, when I'm asking for definition of swank/backend:activate-stepping, I see two suggested source locations: (defvar swank/backend:activate-stepping) (defun swank/backend:activate-stepping) defun is for definterface, defvar is for defimplementation. This works at least in SBCL, I guess it is handy. Patch is attached. This may seem a bit ugly, but SBCL does not suggest a way to extend its definition database with new classes, so I see no good way to go. WBR, Budden

4 10