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

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 27 Apr '04

27 Apr '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.348 slime/ChangeLog:1.352 --- slime/ChangeLog:1.348 Sun Apr 25 02:44:15 2004 +++ slime/ChangeLog Mon Apr 26 17:59:39 2004 @@ -1,3 +1,35 @@ +2004-04-26 Luke Gorrie <luke(a)bluetail.com> + + * swank.lisp: Move definition of `with-io-redirection' above + `with-connection' to avoid a CLISP error. This is really weird. + (interactive-eval): Bind *package* to *buffer-package*, so that + `C-x C-e' and related commands evaluate in the expected package. + + * slime.el (sldb-insert-frames): Handle empty backtrace (I got one + in CLISP). + + * swank-allegro.lisp (arglist): Return :not-available if arglist + lookup fails with an error. + + * slime.el: Moved snippets of Common Lisp code into swank.lisp + from the thread control panel. (Remember, no CL code in slime.el!) + + * swank-loader.lisp (*lisp-name*): Include a short version number + in the Lisp name to separate FASL files for different + versions. Only implemented for CMUCL and SBCL sofar. + + * swank.lisp (ed-in-emacs): Avoid mutating the argument. + (spawn-repl-thread): Add a new thread for evaluating REPL + expressions. This same thread is used for all REPL + evaluation. This fixes some issues with variables like * and ** + in at least SBCL. + + * nregex.lisp: Typo fix (thanks Barry Fishman). + + * slime.el (slime-events-buffer): Don't use hideshow-mode in + XEmacs for the *slime-events* buffer. It causes obscure problems + for some users. Still used in GNU Emacs. + 2004-04-25 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> * swank-backend.lisp (arglist): Return a list or :not-available.

1 0

[slime-devel] SLIME CMUCL restart-frame
by Lynn Quam 26 Apr '04

26 Apr '04

Sorry for the cross-post, but this question is relevent to both the slime-devel and cmucl-imp lists. I used Symbolics Lisp Machines for many years and found it very useful when in the debugger to be able to edit and recompile a function and then restart the call to the function (restart-frame). Is there any chance that SLIME:RESTART-FRAME will be implemented for CMUCL? I guess I do not know the limitations of the CMUCL stack frames and whether this is possible.

2 1

[slime-devel] SLIME eval-xxx inconsistencies
by Lynn Quam 26 Apr '04

26 Apr '04

I noticed that the different eval-xxx commands when executed in a Lisp-mode buffer have different behavior wrt. the treatment of *PACKAGE*. In particular: SLIME-PPRINT-EVAL-LAST-EXPRESSION and SLIME-EVAL-REGION bind *PACKAGE* to SWANK:*BUFFER-PACKAGE*. The other eval-xxx commands do not bind *PACKAGE* and you (apparently) get the value of *PACKAGE* that is bound in slime-repl. It is not clear to me that this difference in behavior is desirable.

2 1

[slime-devel] CLISP SLIME implementation breaks in CVS
by Bill_Clementson＠peoplesoft.com 26 Apr '04

26 Apr '04

My previous SLIME installation was a CVS install from 4/18. I've just taken the latest CVS install and the CLISP SLIME implementation (under Windows) breaks. Here is the error: COERCE: #<MACRO #<COMPILED-CLOSURE SWANK::DEFSLIMEFUN>> cannot be coerced to type FUNCTION [Condition of type SIMPLE-TYPE-ERROR] Restarts: 0: [ABORT] Abort handling SLIME request. Backtrace: 0: EVAL frame for form (SWANK:CREATE-SWANK-SERVER 4007)

2 1

Re: [slime-devel] Re: ACL SLIME implementation breaks in CVS
by Bill_Clementson＠peoplesoft.com 26 Apr '04

26 Apr '04

Luke Gorrie <luke(a)bluetail.com> writes: > Bill_Clementson(a)peoplesoft.com writes: > > > My previous SLIME installation was a CVS install from 4/18. I've just taken > > the latest CVS install and the ACL SLIME implementation (under Windows) > > breaks. Here is the error: > > How about if you hack swank-allegro.lisp with this: > > (defimplementation arglist (symbol) > (handler-case (excl:arglist symbol) > (simple-error () :not-available))) Yep, that did it - thanks! - Bill

1 0

[slime-devel] ACL SLIME implementation breaks in CVS
by Bill_Clementson＠peoplesoft.com 26 Apr '04

26 Apr '04

My previous SLIME installation was a CVS install from 4/18. I've just taken the latest CVS install and the ACL SLIME implementation (under Windows) breaks. Here is the error: EXCL::DEFUN-PROTO-1 is not a function or macro [Condition of type SIMPLE-ERROR] Restarts: 0: [ABORT] Return to sldb level 1. 1: [ABORT] Abort handling SLIME request. 2: [ABORT] Abort entirely from this process. Backtrace: 0: (SWANK::DEBUG-IN-EMACS #<SIMPLE-ERROR @ #x205164f2>) 1: ((FLET SWANK::SWANK-DEBUGGER-HOOK SWANK::DEBUG-IT)) 2: (SWANK::SWANK-DEBUGGER-HOOK #<SIMPLE-ERROR @ #x205164f2> #<Function SWANK-DEBUGGER-HOOK>) 3: (EXCL::INTERNAL-INVOKE-DEBUGGER "Error" #<SIMPLE-ERROR @ #x205164f2> T) 4: (ERROR SIMPLE-ERROR :FORMAT-CONTROL "~s is not a function or macro" :FORMAT-ARGUMENTS (EXCL::DEFUN-PROTO-1)) 5: (EXCL::.ERROR "~s is not a function or macro" EXCL::DEFUN-PROTO-1) 6: (ARGLIST EXCL::DEFUN-PROTO-1) 7: ((METHOD SWANK-BACKEND:ARGLIST (T)) EXCL::DEFUN-PROTO-1) 8: (SWANK::SYMBOL-INDENTATION EXCL::DEFUN-PROTO-1) 9: ((FLET SWANK::UPDATE-INDENTATION/DELTA-FOR-EMACS SWANK::CONSIDER) EXCL::DEFUN-PROTO-1) 10: ((FLET SWANK::UPDATE-INDENTATION/DELTA-FOR-EMACS #:G2216) EXCL::DEFUN-PROTO-1 EXCL::DEFUN-PROTO-1) 11: (MAPHASH #<Closure (FLET SWANK::UPDATE-INDENTATION/DELTA-FOR-EMACS #:G2216) @ #xab2e87a> #<SYMBOL hash-table (sans values) with 5641 entries @ #x2002c5ca>) 12: (SWANK::UPDATE-INDENTATION/DELTA-FOR-EMACS #<EQ hash-table with 45 entries @ #x2049243a> (#<The ACL-SOCKET package> #<The ACLMOP package> #<The COMMON-LISP package> #<The COMMON-LISP-USER package> #<The COMPILER package> #<The CROSS-REFERENCE package> #<The DEBUGGER package> #<The DEFSYSTEM package> #<The EXCL package> #<The EXCL.SCM package> #<The FOREIGN-FUNCTIONS package> #<The G10 package> #<The GARBAGE package> #<The INSPECT package> #<The KEYWORD package> #<The LEP package> #<The LEP-IO package> #<The MULTIPROCESSING package> #<The NET.URI package> #<The NREGEX package> #<The PROFILER package> #<The SWANK package> #<The SWANK-BACKEND package> #<The SWANK-COMPLETION-TEST package> #<The SWANK-IO-PACKAGE package> #<The SWANK-LOADER package> #<The SYSTEM package> #<The TOP-LEVEL package>)) 13: (SWANK::PERFORM-INDENTATION-UPDATE #S(SWANK::CONNECTION :SOCKET-IO #<MULTIVALENT #2=stream socket #3=connected from #1=localhost/4005 to #1#/1622 @ #x204b28fa> :DEDICATED-OUTPUT #4=#<MULTIVALENT #2# #3#connected from #1#/1623 to #1#/1624 @ #x20492cda> :USER-INPUT #<SWANK-BACKEND::SLIME-INPUT-STREAM @ #x204931f2> :USER-OUTPUT #4# :USER-IO #<TWO-WAY-STREAM @ #x204931da> :CONTROL-THREAD #<MULTIPROCESSING:PROCESS control-thread(724)[1] #5=receive @ #x204a480a> :READER-THREAD #<MULTIPROCESSING:PROCESS reader-thread(8e8)[4] waiting for input @ #x204a4782> :REPL-THREAD #<MULTIPROCESSING:PROCESS Anonymous(890)[5] #5# @ #x204a46fa> :READ #<Function READ-FROM-CONTROL-THREAD> :SEND #<Function SEND-TO-CONTROL-THREAD> :SERVE-REQUESTS #<Function SPAWN-THREADS-FOR-CONNECTION> :CLEANUP NIL :INDENTATION-CACHE #<EQ hash-table with 45 entries @ #x2049243a> :INDENTATION-CACHE-PACKAGES NIL) (#<The ACL-SOCKET package> #<The ACLMOP package> #<The COMMON-LISP package> #<The COMMON-LISP-USER package> #<The COMPILER package> #<The CROSS-REFERENCE package> #<The DEBUGGER package> #<The DEFSYSTEM package> #<The EXCL package> #<The EXCL.SCM package> #<The FOREIGN-FUNCTIONS package> #<The G10 package> #<The GARBAGE package> #<The INSPECT package> #<The KEYWORD package> #<The LEP package> #<The LEP-IO package> #<The MULTIPROCESSING package> #<The NET.URI package> #<The NREGEX package> #<The PROFILER package> #<The SWANK package> #<The SWANK-BACKEND package> #<The SWANK-COMPLETION-TEST package> #<The SWANK-IO-PACKAGE package> #<The SWANK-LOADER package> #<The SYSTEM package> #<The TOP-LEVEL package>)) 14: (SWANK::UPDATE-CONNECTION-INDENTATION #S(SWANK::CONNECTION :SOCKET-IO #<MULTIVALENT #2=stream socket #3=connected from #1=localhost/4005 to #1#/1622 @ #x204b28fa> :DEDICATED-OUTPUT #4=#<MULTIVALENT #2# #3#connected from #1#/1623 to #1#/1624 @ #x20492cda> :USER-INPUT #<SWANK-BACKEND::SLIME-INPUT-STREAM @ #x204931f2> :USER-OUTPUT #4# :USER-IO #<TWO-WAY-STREAM @ #x204931da> :CONTROL-THREAD #<MULTIPROCESSING:PROCESS control-thread(724)[1] #5=receive @ #x204a480a> :READER-THREAD #<MULTIPROCESSING:PROCESS reader-thread(8e8)[4] waiting for input @ #x204a4782> :REPL-THREAD #<MULTIPROCESSING:PROCESS Anonymous(890)[5] #5# @ #x204a46fa> :READ #<Function READ-FROM-CONTROL-THREAD> :SEND #<Function SEND-TO-CONTROL-THREAD> :SERVE-REQUESTS #<Function SPAWN-THREADS-FOR-CONNECTION> :CLEANUP NIL :INDENTATION-CACHE #<EQ hash-table with 45 entries @ #x2049243a> :INDENTATION-CACHE-PACKAGES NIL)) 15: (SWANK::SYNC-STATE-TO-EMACS) 16: (SWANK::EVAL-FOR-EMACS (SWANK:BACKTRACE 2 41) NIL 2) 17: (SYSTEM::..RUNTIME-OPERATION . :UNKNOWN-ARGS) 18: (FUNCALL SWANK::EVAL-FOR-EMACS (SWANK:BACKTRACE 2 41) NIL 2) 19: (SYSTEM::..RUNTIME-OPERATION

2 1

[slime-devel] repl-thread
by Luke Gorrie 26 Apr '04

26 Apr '04

Ahoy, I checked in a change so that the REPL has a dedicated thread for evaluating all expressions. Hopefully by reusing the same thread we're less vulnerable to the implementation-specific threading nuances, e.g. now *, +, **, etc are working again in SBCL. It seems to work fine under SBCL and LispWorks. If someone running Franz or OpenMCL could confirm that I didn't break them I'd be much obliged. P.S., I'm finding the multithreading code quite comprehensible with this simple message-passing interface. Nice one Helmut! -Luke

1 0

[slime-devel] Keyboard dropping in nregex.lisp
by Barry Fishman 26 Apr '04

26 Apr '04

Since its been there a while and nobody has fixed it. There is a error in nregex.lisp. Index: nregex.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/nregex.lisp,v retrieving revision 1.1 diff -c -r1.1 nregex.lisp *** nregex.lisp 21 Apr 2004 18:55:24 -0000 1.1 --- nregex.lisp 26 Apr 2004 12:15:06 -0000 *************** *** 256,262 **** ;; ;; If this is the last character of the expression then ;; anchor the end of the expression, otherwise let it slide ! u ;; as a standard character (even though it should be quoted). ;; (if (= eindex (1- (length source))) (add-exp '((if (not (= index length)) --- 256,262 ---- ;; ;; If this is the last character of the expression then ;; anchor the end of the expression, otherwise let it slide ! ;; as a standard character (even though it should be quoted). ;; (if (= eindex (1- (length source))) (add-exp '((if (not (= index length)) -- Barry Fishman

2 1

[slime-devel] cmucl arglist
by Gabor Melis 25 Apr '04

25 Apr '04

(defun foo (x y) (declare (optimize (debug 0))) (+ x y)) In READ-ARGLIST DI::DEBUG-FUNCTION-LAMBDA-LIST signals LAMBDA-LIST-UNAVAILABLE. Naive fix below. Cheers, Gabor Melis Index: swank-cmucl.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/swank-cmucl.lisp,v retrieving revision 1.97 diff -u -r1.97 swank-cmucl.lisp --- swank-cmucl.lisp 21 Apr 2004 19:46:40 -0000 1.97 +++ swank-cmucl.lisp 23 Apr 2004 21:40:01 -0000 @@ -986,10 +986,13 @@ ;; this should work both for ;; compiled-debug-function and for ;; interpreted-debug-function - (t (let ((df (di::function-debug-function fun))) - (if df - (debug-function-arglist df) - "(<arglist-unavailable>)")))))) + (t (let ((df (di::function-debug-function fun)) + (unavailable "(<arglist-unavailable>)")) + (if df + (handler-case (debug-function-arglist df) + (di::lambda-list-unavailable () + unavailable)) + unavailable)))))) (check-type arglist (or list string)) arglist))

2 4

[slime-devel] SIGINT Problems with SLIME in Allegro
by Lynn Quam 25 Apr '04

25 Apr '04

I have been having problems with SIGINT (keyboard interrupts) with SLIME and Allegro 6.0. My SLIME version is a recent (April 21, 04) cvs update using: cvs -d :pserver:anonymous@common-lisp.net:/project/slime/cvsroot co -r \ FAIRLY-STABLE slime Here is what happens when typing C-c C-c into the *inferior-lisp* buffer after starting up Allegro 6.0 (X86). _____________________________________________ International Allegro CL Professional Edition 6.0 [Linux (x86)] (Oct 26, 2000 15:41) Copyright (C) 1985-2000, Franz Inc., Berkeley, CA, USA. All Rights Reserved. ;; Optimization settings: safety 1, space 1, speed 1, debug 2. ;; For a complete description of all compiler switches given the ;; current optimization settings evaluate (EXPLAIN-COMPILER-SETTINGS). CL-USER(1): ; Loading /m/rom1/downloads/slime/slime/swank-loader.lisp ; Fast loading ; /m/rom1/downloads/slime/slime/fasl/allegro/swank-backend.fasl ; Fast loading /m/rom1/downloads/slime/slime/fasl/allegro/nregex.fasl ; Fast loading ; /m/rom1/downloads/slime/slime/fasl/allegro/swank-allegro.fasl Warning: (METHOD DESCRIBE-DEFINITION (T T)) is defined more than once as a operator in the file /m/rom1/downloads/slime/slime/swank-allegro.lisp. ; Fast loading ; /m/rom1/downloads/slime/slime/fasl/allegro/swank-gray.fasl ; Fast loading /m/rom1/downloads/slime/slime/fasl/allegro/swank.fasl Warning: These Swank interfaces are unimplemented: (ADD-FD-HANDLER ADD-SIGIO-HANDLER CALL-WITH-COMPILATION-HOOKS LIST-CALLERS PROFILE PROFILE-PACKAGE PROFILE-REPORT PROFILE-RESET PROFILED-FUNCTIONS REMOVE-FD-HANDLERS REMOVE-SIGIO-HANDLERS UNPROFILE WHO-SPECIALIZES) ; Loading /homedir/quam/.swank.lisp T CL-USER(2): ;; Swank started at port: 60573. 60573 CL-USER(3): t T CL-USER(4): Interrupt 2 (Keyboard interrupt): Select a process to handle it: 0 -- Ignore the Interrupt -- 1 #<MULTIPROCESSING:PROCESS Initial Lisp Listener waiting for input @ #x200f9e6a> 2 #<MULTIPROCESSING:PROCESS control-thread receive @ #x205dac7a> 3 #<MULTIPROCESSING:PROCESS reader-thread waiting for input @ #x205dad42> The scheduler is attempting to recover from Process-wait may not be called within the scheduler's stack group.. 1 1 CL-USER(5): Interrupt 2 (Keyboard interrupt): Select a process to handle it: 0 -- Ignore the Interrupt -- 1 #<MULTIPROCESSING:PROCESS Initial Lisp Listener waiting for input @ #x200f9e6a> 2 #<MULTIPROCESSING:PROCESS control-thread receive @ #x205dac7a> 3 #<MULTIPROCESSING:PROCESS reader-thread waiting for input @ #x205dad42> The scheduler is attempting to recover from Process-wait may not be called within the scheduler's stack group.. Error: Process-wait may not be called within the scheduler's stack group. [condition type: SIMPLE-ERROR] Error: Process-wait may not be called within the scheduler's stack group. [condition type: SIMPLE-ERROR] ... Error: Process-wait may not be called within the scheduler's stack group. [condition type: SIMPLE-ERROR] Error: Recursive error while printing or signalling an error. This is sometimes caused by an error in a print-object method. ;; Exiting lisp because of too many consecutive errors... ;; Exiting lisp because of too many consecutive errors... ... _____________________________________________ Do other Allegro SLIME users have this problem also?

2 1