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

[slime-devel] Manual labour
by Luke Gorrie 24 Mar '04

24 Mar '04

[Repost: I'm not sure that my via-Gmane post is getting through.] I've drafted a user manual in doc/slime.texi. It's also online at http://www.bluetail.com/~luke/misc/lisp/slime.ps.gz http://www.bluetail.com/~luke/misc/lisp/slime.pdf The PDF version is a bit ugly (from ps2pdf), because texi2pdf is choking on slime.texi for some reason. Feedback would be welcome, so please RTFM! Cheers, Luke

4 7

[slime-devel] Tab completion bug?
by Dirk Gerrits 24 Mar '04

24 Mar '04

Typing M, U, L, <TAB> in the SLIME REPL produces "multiple-value|-" where | represents the cursor/point. Is this a bug? If it'd produce "multiple-value-|" then "multiple-value-bind" and such would be just a tad easier to type. Regards, Dirk Gerrits

4 9

[slime-devel] getpid implementation on sbcl
by Christophe Rhodes 24 Mar '04

24 Mar '04

May be of interest. (Mostly because it removes the warning at startup, but also using the sb-posix supported function rather than the sb-unix internal one. Cheers, Christophe -- http://www-jcsu.jesus.cam.ac.uk/~csr21/ +44 1223 510 299/+44 7729 383 757 (set-pprint-dispatch 'number (lambda (s o) (declare (special b)) (format s b))) (defvar b "~&Just another Lisp hacker~%") (pprint #36rJesusCollegeCambridge)

1 0

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

24 Mar '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.302 slime/ChangeLog:1.303 --- slime/ChangeLog:1.302 Mon Mar 22 11:35:57 2004 +++ slime/ChangeLog Tue Mar 23 16:38:48 2004 @@ -1,3 +1,56 @@ +2004-03-23 Alan Shutko <ats(a)acm.org> + + * swank-clisp.lisp (set-default-directory): New function. + +2004-03-23 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * swank-allegro.lisp (send): Wait a bit if there are already many + message in the mailbox. + + * swank-clisp.lisp (xref-results): Use fspec-location instead of + the of fspec-source-locations. Reported by Alan Shutko. + (break): Be friendly to case-inverting readtables. + + * swank-lispworks.lisp (emacs-connected): Add default method to + environment-display-notifier. Reported by Bjørn Nordbø. + (set-default-directory, who-specializes): Implemented for + Lispworks. + (gfp): New function. + (describe-symbol-for-emacs, describe-definition): Distinguish + between ordinary and generic functions. + (call-with-debugging-environment): Unwind a few frames. Looks + better and avoids the problems with the real topframe. + (interesting-frame-p): Use Lispworks dbg:*print-xxx* variables to + decide which frames are interesting. + (frame-actual-args): New function. + (print-frame): Use it. + + * swank.lisp (open-streams, make-output-function): Capture the + connection not only the socket. This way the streams can be used + from unrelated threads. Reported by Alain Picard. + (create-connection): Factorized. Initialize the streams after the + connection is created. + (initialize-streams-for-connection, spawn-threads-for-connection): + New functions. + (with-connection): Fix quoting bug and move upwards before first + use. + (send-output-to-emacs): Add kludge for SBCL !-package names. + (apropos-list-for-emacs): Lispworks apparently returns duplicates; + remove them. + (inspect-object): Princ the label to allow strings and symbols. + (send-output-to-emacs): Deleted. + (defslimefun-unimplemented): Deleted. Was unused. + + * slime.el (slime-easy-menu): Add some more commands. + (slime-changelog-date): New variable. Initialized with the value + returned by the function of the same name. This detects + incompatible versions if Emacs has not been restarted after an + upgrade. + (slime-check-protocol-version, slime-init-output-buffer): Use it. + (slime-events-buffer, slime-log-event): Use fundamental mode + instead of lisp-mode to avoid excessive font-locking for messages + with lots of strings. + 2004-03-22 Luke Gorrie <luke(a)bluetail.com> * doc/slime.texi: New user manual.

1 0

[slime-devel] possible bug in SLIME/Lispworks
by Bjørn Nordbø 23 Mar '04

23 Mar '04

... or maybe I'm just doing something wrong, but every time a break is evaluated, the following happens: CL-USER> (break) Error: No applicable methods for #<STANDARD-GENERIC-FUNCTION ENVIRONMENT-INTERNALS:ENVIRONMENT-DISPLAY-NOTIFIER 102376E2> with args (#<ENVIRONMENT:TTY-ENVIRONMENT 10218C3F> :CONDITION #<SIMPLE-ERROR 100ACE73> :RESTARTS (#<RESTART CONTINUE 100ABE1B> #<RESTART CONTINUE 100F55F7> #<RESTART CONTINUE 100FF51F> #<RESTART CONTINUE 10107FEB> #<RESTART CONTINUE 100E9EDF> #<RESTART CONTINUE 100E04F3> #<RESTART CONTINUE 100E4427> #<RESTART CONTINUE 10CEFB8B> #<RESTART ABORT 10CEFBC3>)) 1 (continue) Call #<STANDARD-GENERIC-FUNCTION ENVIRONMENT-INTERNALS:ENVIRONMENT-DISPLAY-NOTIFIER 102376E2> again 2 Call #<STANDARD-GENERIC-FUNCTION ENVIRONMENT-INTERNALS:ENVIRONMENT-DISPLAY-NOTIFIER 102376E2> again 3 Call #<STANDARD-GENERIC-FUNCTION ENVIRONMENT-INTERNALS:ENVIRONMENT-DISPLAY-NOTIFIER 102376E2> again 4 Call #<STANDARD-GENERIC-FUNCTION ENVIRONMENT-INTERNALS:ENVIRONMENT-DISPLAY-NOTIFIER 102376E2> again 5 Call #<STANDARD-GENERIC-FUNCTION ENVIRONMENT-INTERNALS:ENVIRONMENT-DISPLAY-NOTIFIER 102376E2> again 6 Call #<STANDARD-GENERIC-FUNCTION ENVIRONMENT-INTERNALS:ENVIRONMENT-DISPLAY-NOTIFIER 102376E2> again 7 Call #<STANDARD-GENERIC-FUNCTION ENVIRONMENT-INTERNALS:ENVIRONMENT-DISPLAY-NOTIFIER 102376E2> again 8 Call #<STANDARD-GENERIC-FUNCTION ENVIRONMENT-INTERNALS:ENVIRONMENT-DISPLAY-NOTIFIER 102376E2> again 9 Return from break. 10 (abort) Return to SLIME toplevel. Type :b for backtrace, :c <option number> to proceed, or :? for other options CL-USER 6 : 9 > I have tried bothe with the latest SLIME and FAIRLY-STABLE and both Lispworks 4.2 and 4.3, but it breaks every time I try. I'm baffled, and any hints about what might be wrong is most welcome. I'm running Lispworks/Solaris and Emacs 21.2.1 btw. I have tried playing around in order to understand what goes wrong, an it seems to me like Lispworks is in error. However breaking works fine outside of SLIME, ie. from the *inferior-lisp*. Here's the backtrace in case anyone can see anything interesting. Call to ERROR Call to CERROR Call to (METHOD NO-APPLICABLE-METHOD (T)) Call to CLOS::APPLY-NO-APPLICABLE-METHOD Call to ENVIRONMENT:DISPLAY-NOTIFIER Call to INVOKE-DEBUGGER Call to ERROR Call to CERROR Call to (METHOD NO-APPLICABLE-METHOD (T)) Call to CLOS::APPLY-NO-APPLICABLE-METHOD Call to ENVIRONMENT:DISPLAY-NOTIFIER Call to INVOKE-DEBUGGER Call to ERROR Call to CERROR Call to (METHOD NO-APPLICABLE-METHOD (T)) Call to CLOS::APPLY-NO-APPLICABLE-METHOD Call to ENVIRONMENT:DISPLAY-NOTIFIER Call to INVOKE-DEBUGGER Call to ERROR Call to CERROR Call to (METHOD NO-APPLICABLE-METHOD (T)) Call to CLOS::APPLY-NO-APPLICABLE-METHOD Call to ENVIRONMENT:DISPLAY-NOTIFIER Call to INVOKE-DEBUGGER Call to ERROR Call to CERROR Call to (METHOD NO-APPLICABLE-METHOD (T)) Call to CLOS::APPLY-NO-APPLICABLE-METHOD Call to ENVIRONMENT:DISPLAY-NOTIFIER Call to INVOKE-DEBUGGER Call to ERROR Call to CERROR Call to (METHOD NO-APPLICABLE-METHOD (T)) Call to CLOS::APPLY-NO-APPLICABLE-METHOD Call to ENVIRONMENT:DISPLAY-NOTIFIER Call to INVOKE-DEBUGGER Call to ERROR Call to CERROR Call to (METHOD NO-APPLICABLE-METHOD (T)) Call to CLOS::APPLY-NO-APPLICABLE-METHOD Call to ENVIRONMENT:DISPLAY-NOTIFIER Call to INVOKE-DEBUGGER Call to ERROR Call to CERROR Call to (METHOD NO-APPLICABLE-METHOD (T)) Call to CLOS::APPLY-NO-APPLICABLE-METHOD Call to ENVIRONMENT:DISPLAY-NOTIFIER Call to INVOKE-DEBUGGER Call to BREAK Call to EVAL Call to SWANK::EVAL-REGION Call to SWANK:LISTENER-EVAL Call to EVAL Call to SWANK::EVAL-FOR-EMACS Call to FUNCALL Call to SWANK::READ-FROM-EMACS Call to (SUBFUNCTION 2 SWANK::HANDLE-REQUEST) Call to SWANK::CALL-WITH-REDIRECTED-IO Call to SWANK::HANDLE-REQUEST Call to (SUBFUNCTION 1 SWANK::DISPATCH-EVENT) Call to (SUBFUNCTION MP::PROCESS-SG-FUNCTION MP::INITIALIZE-PROCESS-STACK) CL-USER 7 : 9 > -- Lisp can accomodate a wide range of psychological problems.

1 1

[slime-devel] CLISP: xref-results missing fspec-source-locations
by Alan Shutko 23 Mar '04

23 Mar '04

In current CVS on CLISP, xref-results (function the CLISP backend uses for who-calls results) doesn't work, because it calls fspec-source-locations which was removed by Helmut on March 10. Helmut, could you take a look at xref-results in swank-clisp and see if it can be converted easily to the new code? I don't immediately understand how that section works, so if you can fix it easily, it would be great. -- Alan Shutko <ats(a)acm.org> - I am the rocks. If I were really two faced, would I be wearing this one?

1 0

[slime-devel] CLISP set-default-directory
by Alan Shutko 23 Mar '04

23 Mar '04

2004-03-23 Alan Shutko <ats(a)acm.org> * swank-clisp.lisp (set-default-directory): New function. --- swank-clisp.lisp.~1.27.~ 2004-03-19 13:01:04.256161600 -0600 +++ swank-clisp.lisp 2004-03-23 13:33:07.746483200 -0600 @@ -62,6 +62,10 @@ (defimplementation lisp-implementation-type-name () "clisp") +(defimplementation set-default-directory (directory) + (setf (ext:default-directory) directory) + (namestring (setf *default-pathname-defaults* (ext:default-directory)))) + ;;; TCP Server -- Alan Shutko <ats(a)acm.org> - I am the rocks. If you quit cold turkey, do you eat hot chicken?

1 0

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

23 Mar '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.300 slime/ChangeLog:1.302 --- slime/ChangeLog:1.300 Sat Mar 20 13:56:38 2004 +++ slime/ChangeLog Mon Mar 22 11:35:57 2004 @@ -1,3 +1,12 @@ +2004-03-22 Luke Gorrie <luke(a)bluetail.com> + + * doc/slime.texi: New user manual. + + * swank.lisp (*communication-style*): New name for + *swank-in-background*. + Exported configuration variables: *communication-style*, + *log-events*, *use-dedicated-output-stream*. + 2004-03-20 Julian Stecklina <der_julian(a)web.de> * swank-sbcl.lisp (+o_async+, +f_setown+, +f_setfl+): Add correct @@ -2283,7 +2292,7 @@ (completer-message): Cut dependency on undefined ilisp constant testing for xemacs. -2003-11-27 Zach <xach(a)xach.com> +2003-11-27 Zach Beane <xach(a)xach.com> * swank.lisp (completions): Complete compound symbols (see below).

1 0

[slime-devel] Weirdness on Lispworks
by Alain.Picard＠memetrics.com 23 Mar '04

23 Mar '04

Recently, SLIME has started exploding for me on lispworks: I get backtraces like this: ================================================================ Error: NIL is not of type SWANK::CONNECTION when accessing slot SWANK-BACKEND:SEND. 1 (abort) Return to level 8. 2 Return to debug level 8. 3 Return to level 7. 4 Return to debug level 7. 5 Return to level 6. 6 Return to debug level 6. 7 Return to level 5. 8 Return to debug level 5. 9 Return to level 4. 10 Return to debug level 4. 11 Return to level 3. 12 Return to debug level 3. 13 Return to level 2. 14 Return to debug level 2. 15 Return to level 1. 16 Return to debug level 1. 17 Return to level 0. 18 Return to top loop level 0. Type :b for backtrace, :c <option number> to proceed, or :? for other options XOS 1 : 9 > :b Call to SWANK::SEND-TO-EMACS Call to SWANK::READ-USER-INPUT-FROM-EMACS Call to (METHOD STREAM:STREAM-READ-CHAR (SWANK-BACKEND::SLIME-INPUT-STREAM)) Call to (METHOD STREAM:STREAM-READ-LINE (STREAM:FUNDAMENTAL-STREAM)) Call to (METHOD STREAM:STREAM-FILL-BUFFER (SYSTEM::LINE-BUFFER-STREAM)) Call to (METHOD STREAM:STREAM-READ-CHAR (STREAM:BUFFERED-STREAM)) Call to IO::READ-OBJECT Call to IO::RECURSIVE-READ Call to READ-PRESERVING-WHITESPACE Call to INVOKE-DEBUGGER Call to SWANK::SEND-TO-EMACS Call to SWANK::READ-USER-INPUT-FROM-EMACS Call to (METHOD STREAM:STREAM-READ-CHAR (SWANK-BACKEND::SLIME-INPUT-STREAM)) Call to (METHOD STREAM:STREAM-READ-LINE (STREAM:FUNDAMENTAL-STREAM)) Call to (METHOD STREAM:STREAM-FILL-BUFFER (SYSTEM::LINE-BUFFER-STREAM)) Call to (METHOD STREAM:STREAM-READ-CHAR (STREAM:BUFFERED-STREAM)) Call to IO::READ-OBJECT Call to IO::RECURSIVE-READ Call to READ-PRESERVING-WHITESPACE Call to INVOKE-DEBUGGER Call to SWANK::SEND-TO-EMACS Call to SWANK::READ-USER-INPUT-FROM-EMACS Call to (METHOD STREAM:STREAM-READ-CHAR (SWANK-BACKEND::SLIME-INPUT-STREAM)) Call to (METHOD STREAM:STREAM-READ-LINE (STREAM:FUNDAMENTAL-STREAM)) Call to (METHOD STREAM:STREAM-FILL-BUFFER (SYSTEM::LINE-BUFFER-STREAM)) Call to (METHOD STREAM:STREAM-READ-CHAR (STREAM:BUFFERED-STREAM)) Call to IO::READ-OBJECT Call to IO::RECURSIVE-READ Call to READ-PRESERVING-WHITESPACE Call to INVOKE-DEBUGGER Call to SWANK::SEND-TO-EMACS Call to SWANK::READ-USER-INPUT-FROM-EMACS Call to (METHOD STREAM:STREAM-READ-CHAR (SWANK-BACKEND::SLIME-INPUT-STREAM)) Call to (METHOD STREAM:STREAM-READ-LINE (STREAM:FUNDAMENTAL-STREAM)) Call to (METHOD STREAM:STREAM-FILL-BUFFER (SYSTEM::LINE-BUFFER-STREAM)) Call to (METHOD STREAM:STREAM-READ-CHAR (STREAM:BUFFERED-STREAM)) Call to IO::READ-OBJECT Call to IO::RECURSIVE-READ Call to READ-PRESERVING-WHITESPACE Call to INVOKE-DEBUGGER Call to SWANK::SEND-TO-EMACS Call to SWANK::READ-USER-INPUT-FROM-EMACS Call to (METHOD STREAM:STREAM-READ-CHAR (SWANK-BACKEND::SLIME-INPUT-STREAM)) Call to (METHOD STREAM:STREAM-READ-LINE (STREAM:FUNDAMENTAL-STREAM)) Call to (METHOD STREAM:STREAM-FILL-BUFFER (SYSTEM::LINE-BUFFER-STREAM)) Call to (METHOD STREAM:STREAM-READ-CHAR (STREAM:BUFFERED-STREAM)) Call to IO::READ-OBJECT Call to IO::RECURSIVE-READ Call to READ-PRESERVING-WHITESPACE Call to INVOKE-DEBUGGER Call to SWANK::SEND-TO-EMACS Call to SWANK::READ-USER-INPUT-FROM-EMACS Call to (METHOD STREAM:STREAM-READ-CHAR (SWANK-BACKEND::SLIME-INPUT-STREAM)) Call to (METHOD STREAM:STREAM-READ-LINE (STREAM:FUNDAMENTAL-STREAM)) Call to (METHOD STREAM:STREAM-FILL-BUFFER (SYSTEM::LINE-BUFFER-STREAM)) Call to (METHOD STREAM:STREAM-READ-CHAR (STREAM:BUFFERED-STREAM)) Call to IO::READ-OBJECT Call to IO::RECURSIVE-READ Call to READ-PRESERVING-WHITESPACE Call to INVOKE-DEBUGGER Call to SWANK::SEND-TO-EMACS Call to SWANK::READ-USER-INPUT-FROM-EMACS Call to (METHOD STREAM:STREAM-READ-CHAR (SWANK-BACKEND::SLIME-INPUT-STREAM)) Call to (METHOD STREAM:STREAM-READ-LINE (STREAM:FUNDAMENTAL-STREAM)) Call to (METHOD STREAM:STREAM-FILL-BUFFER (SYSTEM::LINE-BUFFER-STREAM)) Call to (METHOD STREAM:STREAM-READ-CHAR (STREAM:BUFFERED-STREAM)) Call to IO::READ-OBJECT Call to IO::RECURSIVE-READ Call to READ-PRESERVING-WHITESPACE Call to INVOKE-DEBUGGER Call to SWANK::SEND-TO-EMACS Call to SWANK::READ-USER-INPUT-FROM-EMACS Call to (METHOD STREAM:STREAM-READ-CHAR (SWANK-BACKEND::SLIME-INPUT-STREAM)) Call to (METHOD STREAM:STREAM-READ-LINE (STREAM:FUNDAMENTAL-STREAM)) Call to (METHOD STREAM:STREAM-FILL-BUFFER (SYSTEM::LINE-BUFFER-STREAM)) Call to (METHOD STREAM:STREAM-READ-CHAR (STREAM:BUFFERED-STREAM)) Call to IO::READ-OBJECT Call to IO::RECURSIVE-READ Call to READ-PRESERVING-WHITESPACE Call to INVOKE-DEBUGGER Call to SWANK::SEND-TO-EMACS Call to SWANK::READ-USER-INPUT-FROM-EMACS Call to (METHOD STREAM:STREAM-READ-CHAR (SWANK-BACKEND::SLIME-INPUT-STREAM)) Call to IO::READ-OBJECT Call to IO::RECURSIVE-READ Call to READ-PRESERVING-WHITESPACE Call to EDITOR:RUBBER-READ-A-COMMAND Call to (HARLEQUIN-COMMON-LISP:SUBFUNCTION MP::PROCESS-SG-FUNCTION MP::INITIALIZE-PROCESS-STACK) XOS 2 : 9 > ================================================================ I traced the error to the following form in my code: (setq *top-level-listener-process* (run-safe-thread "Debug Listener" ; name nil ; keywords #'system::listener-top-level ; function user::*terminal-io*)) So, I conditionalized my application to simply not do this when running under SLIME (i.e. in development mode). This is not a bug report (or even a complaint!) just an observation that something which used to work no longer does so. I can imagine why replacing the top level listener from behind SLIME's back may not be a good thing. Perhaps all this is really is a note so that someday, the mechanism by which SLIME communicates with the back ends will be sufficiently well documented that it can say somewhere in the manual that forms like the above are not a good idea if you want to use slime. :-) p.s. Slime juss keeps on gettin' better! Great work!

1 0

[slime-devel] Manual labour
by Luke Gorrie 22 Mar '04

22 Mar '04

Hiho, I've drafted a user manual in doc/slime.texi. It's also online at http://www.bluetail.com/~luke/misc/lisp/slime.ps.gz http://www.bluetail.com/~luke/misc/lisp/slime.pdf The PDF version is a bit ugly (from ps2pdf), because texi2pdf is choking on slime.texi for some reason. Feedback would be welcome, so please RTFM! Cheers, Luke

1 0