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

[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

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

25 Apr '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.347 slime/ChangeLog:1.348 --- slime/ChangeLog:1.347 Fri Apr 23 18:13:08 2004 +++ slime/ChangeLog Sun Apr 25 02:44:15 2004 @@ -1,3 +1,21 @@ +2004-04-25 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * swank-backend.lisp (arglist): Return a list or :not-available. + Don't return strings or raise exceptions. + + * swank.lisp (arglist-for-echo-area): Simplified and adapted for + the new semantic of ARGLIST. + (arglist-for-insertion): Now a separate function. + (read-arglist): Deleted. No longer needed. + + * swank-cmucl.lisp, swank-lispworks.lisp (arglist): Return + :not-available if the arglist cannot be determined. + + * slime.el (slime-set-connection-info): Hide the *inferior-lisp* + buffer here, so that we have all the buffer rearrangement in one + place. + (slime-insert-arglist): Use swank:arglist-for-insertion. + 2004-04-24 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> * slime.el (slime-init-connection-state): Use an asynchronous RPC

1 0

[slime-devel] reconnect slime to lisp
by David Steuber 25 Apr '04

25 Apr '04

If you enter my subject line into Google and are feeling lucky, you will find Bill Clemontson's blog on the subject. I had slightly different needs than what he described though. Here's my deal. Using a script, I want to start up a lisp session that runs as a web application server on a remote host. At arbitrary times, I wish to be able to connect to this lisp session and modify the running process. I connect to the remote host using the 'ssh -X' command and run Emacs from there. That is the Emacs I want to connect to my running lisp. I'm using SBCL on Linux (Debian/testing with my own 2.6.5 kernel). The SBCL is from CVS with sb-thread and sb-futex enabled. I've got KMR's cl-modlisp standing in for my application server at the moment. Its debug page is a good way to test that I've got Apache talking to SBCL. I'm also using detachtty. I find this very convenient. Basicly, my only remaining problem (other than writing web applications) is to create a run control script for /etc/init.d/ so that SBCL can be started, stopped, and restarted in the same fashion as apache. This seems to be working. This makes me very happy. I suppose I should mention that I have an sbclrc file that requires asdf and asdf-install. I am also using the var for the swank communication style rather than assuming :spawn. This works because the symbol was exported. The anounce-fn was not exported. I am using a simple lambda because it really doesn't need to do anything. Here is the script: #!/bin/sh # # Start SBCL as a detachtty process and start listening to Apache # # Swank is used so that SLIME can connect to the running process at # any time. Consider this a huge security hole. # rm /home/david/usr/var/run/lisp-dribble 2>/dev/null rm /home/david/usr/var/run/detachtty.log 2>/dev/null rm /home/david/usr/var/run/lisp.pid 2>/dev/null rm /home/david/usr/var/run/lisp-socket 2>/dev/null export SBCL_HOME=/home/david/usr/lib/sbcl /usr/bin/detachtty --dribble-file /home/david/usr/var/run/lisp-dribble \ --log-file /home/david/usr/var/run/detachtty.log \ --pid-file /home/david/usr/var/run/lisp.pid \ /home/david/usr/var/run/lisp-socket \ /home/david/usr/bin/sbcl \ --eval "(asdf:operate 'asdf:load-op :modlisp)" \ --eval "(asdf:operate 'asdf:load-op :swank)" \ --eval "(ml:modlisp-start :port 3000)" \ --eval "(swank:create-swank-server 4005 swank:*communication-style* #'(lambda (p) p) t)" -- I wouldn't mind the rat race so much if it wasn't for all the damn cats.

1 0

[slime-devel] Hyperdoc directions
by Nikodemus Siivola 24 Apr '04

24 Apr '04

First some background to get everyone up to speed: Hyperdoc is a project to provide CLHS-style documentation lookup for libraries. http://www.common-lisp.net/project/hyperdoc/ Edi Weitz recently added support for the hyperdoc protocol to his packages, and the hyperdoc CVS contains horrid buggy hack in slime.patch which replaces the clhs lookup in Slime by similar functionality powered by hyperdoc. (Hyperdoc delegates undocumented symbols to hyperspec-lookup <http://www.common-lisp.net/project/hyperspec-lookup/>.) Calling (hyperdoc:lookup package-name symbol-name &optional doc-type-name) gives either NIL, an URI, or if multiple docs for the same symbol exist an alist of the form ((doc-type-name . uri)*). The URIs related to a package can be stared in files, and if this has been done with (hyperdoc:generate-index package), then lookup can be done even if the package is not loaded. The idea is that these lookup files could also be used directly by Slime/Emacs if it isn't connected to a lisp. In it's current state it's basically usable, but some refinements are probably necessary for serious use: 1) Hook the index generation to compiling, either by doing (eval-when (:compile-toplevel) (when (find-package :hyperdoc) (funcall (intern "GENERATE-INDEX" :hyperdoc) :this-package))) in client packages, or maybe/preferebly this could be delegated to ASDF. 2) Do the Emacs/Slime binding: * If connected use hyperdoc. * If not connected use the indices and hyperspec.el. * When the query gives multiple results (eg. a structure and a function of the same name) prompt the user to choose which type of documentation should be fetched. "Fair enough, but get to the point already!" Ok, ok... Do people have ideas/opinions on number 1? Once it is done, I think essentially all work on the CL side is complete. Then, if desired, the API can be integrated with cl:documentation or asdf:hyperdocumentation. What do Slime folks think of the Emacs integration? Is someone willing to do the grunt work on it? As the patch to current Slime shows, my elisp-fu and slime-fu are rather lacking. Anything I've forgotten? Cheers, -- Nikodemus

2 1

[slime-devel] Resizing Emacs frame just after starting SLIME
by Paolo Amoroso 24 Apr '04

24 Apr '04

When I start SLIME and resize the Emacs main frame via the window manager's maximize button, the Emacs windows (e.g. those associated with the *scratch* and *slime-repl[1]* buffers) do not adapt to the new size. They remain in the initial configuration. But as soon as I press any key, the windows instantly get the correct size and location. I am using SLIME CVS sources updated a few hours ago, CMUCL 18e and GNU Emacs 20.7.2 under Debian Woody. Paolo -- Why Lisp? http://alu.cliki.net/RtL%20Highlight%20Film

3 4

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

24 Apr '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.345 slime/ChangeLog:1.347 --- slime/ChangeLog:1.345 Thu Apr 22 17:43:34 2004 +++ slime/ChangeLog Fri Apr 23 18:13:08 2004 @@ -1,3 +1,19 @@ +2004-04-24 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * slime.el (slime-init-connection-state): Use an asynchronous RPC + instead of slime-eval to reduce the amount of work we do in the + timer function. We can remove the workaround for the timer + problem. + +2004-04-23 Luke Gorrie <luke(a)bluetail.com> + + * slime.el: Updated top comments. + Make SLIME faces inherit from their font-lock cousins properly. + (slime-connect): Bind `slime-dispatching-connection' to avoid + being confused by old buffer-local variables when initializing + the connection. This fixes a bug where doing `M-x slime' from the + REPL could give a "Not connected" error. + 2004-04-22 Edi Weitz <edi(a)agharta.de> * slime.el (slime-read-system-name): Perform completion on all

1 0

[slime-devel] list-all-package-names, really all... :)
by Edi Weitz 23 Apr '04

23 Apr '04

Here's another tiny patch. It seems that the function SWANK:LIST-ALL-PACKAGE-NAMES is only used for slime-read-package-name. What about extending it such that nicknames can also be entered? See below. Cheers, Edi.

3 3

[slime-devel] Installation Slime with OpenMCL
by jsdey＠optonline.net 23 Apr '04

23 Apr '04

Greetings: I wanted to fool around with slime to learn lisp. I am caught in a dilemma like which came first the chicken or the egg. Right now the contents of slime.el is unfathonable to me because I am not familiar with the list syntacs. It looks like I am unable to launch swank because a path spec may be in error. I am sorry to bother you with this request but I am hoping someone will take pity on me and give me a little advise. Thanks BACKGROUND When I enter "M-x slime" in emacs, the following message appears: apply: Specified program for new process is a directory Emacs: GNU Emacs 21.3.50.2 (powerpc-apple-darwin7.0.0) of 2003-11-14 on marx.local Snippit from .emacs (setq inferior-lisp-program "/Applications/Emacs.app/Contents/Resources/share/emacs/21.3.50/lisp") (add-to-list 'load-path "/Users/robo2/Lisp/slime") (require 'slime) (add-hook 'lisp-mode-hook (lambda () (slime-mode t))) (add-hook 'inferior-lisp-mode-hook (lambda () (inferior-slime-mode t))) OpenMCL: Welcome to OpenMCL Version (Beta: Darwin) 0.14.1-p1! Command "openmcl" launches interpreter. Slime: robo2:~/lisp/slime/CVS robo2$ less Entries /ChangeLog/1.343/Wed Apr 21 22:58:34 2004// /HACKING/1.5/Mon Mar 29 00:59:38 2004// /README/1.9/Tue Nov 25 00:22:36 2003// /hyperspec.el/1.2/Thu Dec 4 16:42:53 2003// /metering.lisp/1.1/Wed Feb 18 07:25:38 2004// /nregex.lisp/1.1/Wed Apr 21 18:55:24 2004// /slime.el/1.271/Wed Apr 21 22:59:04 2004// /swank-allegro.lisp/1.29/Wed Apr 7 16:35:20 2004// /swank-backend.lisp/1.43/Wed Apr 14 18:50:36 2004// /swank-clisp.lisp/1.29/Tue Apr 6 10:42:53 2004// /swank-cmucl.lisp/1.97/Wed Apr 21 19:46:40 2004// /swank-gray.lisp/1.5/Tue Mar 9 19:35:36 2004// /swank-lispworks.lisp/1.38/Sat Mar 27 21:17:36 2004// /swank-loader.lisp/1.21/Wed Apr 21 18:56:42 2004// /swank-openmcl.lisp/1.72/Tue Apr 6 10:42:53 2004// /swank-sbcl.lisp/1.83/Tue Apr 6 10:42:53 2004// /swank-source-path-parser.lisp/1.5/Mon Mar 29 17:49:38 2004// /swank.asd/1.2/Thu Jan 22 00:10:39 2004// /swank.lisp/1.170/Wed Apr 21 21:51:23 2004// /test-all.sh/1.1/Tue Mar 9 20:12:43 2004// /test.sh/1.6/Sat Jan 31 11:50:25 2004// /xref.lisp/1.1/Fri Jan 2 08:17:15 2004// System: Mac OS X v 10.3.3 -- Dual 2 GHz PowerPC G5

6 8

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

23 Apr '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.343 slime/ChangeLog:1.345 --- slime/ChangeLog:1.343 Wed Apr 21 18:58:34 2004 +++ slime/ChangeLog Thu Apr 22 17:43:34 2004 @@ -1,3 +1,17 @@ +2004-04-22 Edi Weitz <edi(a)agharta.de> + + * slime.el (slime-read-system-name): Perform completion on all + systems in the central registry. + + * swank.lisp (list-all-systems-in-central-registry): New function. + +2004-04-22 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * slime.el (slime-repl-update-banner): Add workaround to force the + proper behavior of the the first command in the REPL buffer. + (slime-repl-shortcut-history): Define the variable to make XEmacs + happy. + 2004-04-22 Tiago Maduro-Dias <tcmd(a)rnl.ist.utl.pt> * slime.el (slime-space): Cleanup.

1 0

[slime-devel] slime-read-system-name
by Edi Weitz 22 Apr '04

22 Apr '04

Here's a patch to allow for completion in shortcut operations which deal with ASDF systems. It's sub-optimal because it only checks ASDF's central registry but I don't think it's possible to write a general solution in the presence of ASDF:*SYSTEM-DEFINITION-SEARCH-FUNCTIONS*. I was about to write that I doubt anybody uses custom search functions anyway and that I myself had never heard of them. But then I remembered that I had: <http://weitz.de/asdf-install/#load-asdf-install> :) Anyway, here's the patch. Cheers, Edi.

2 3

Re: [slime-devel] errors on startup
by Helmut Eller 22 Apr '04

22 Apr '04

Artem Baguinski <artm(a)v2.nl> writes: > plus this *Compile-Log* buffer flushed for a split second. > I understand that warning is something to expect in a alpha version > of the software, but i still suspect i'm doing something > wrong... e.g. compiling slime every time i (require) it. could that > be helped? We byte-compile some performance critical functions at load time, this is why you see the warnings every time. I don't see the warnings, tough. Neither in CVS Emacs nor in Emacs 20. Could you find out which functions cause the warnings? Just byte-compile the file and press RET in the *Compile-Log* buffer over the warning. Helmut.

2 3

[slime-devel] hyperspec-addon.el
by Edi Weitz 22 Apr '04

22 Apr '04

In case you haven't seen this on c.l.l: <http://homepage1.nifty.com/bmonkey/emacs/elisp/hyperspec-addon.el> I think it should be added to SLIME. Edi.

2 2

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

22 Apr '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.341 slime/ChangeLog:1.343 --- slime/ChangeLog:1.341 Tue Apr 20 18:38:59 2004 +++ slime/ChangeLog Wed Apr 21 18:58:34 2004 @@ -1,3 +1,42 @@ +2004-04-22 Tiago Maduro-Dias <tcmd(a)rnl.ist.utl.pt> + + * slime.el (slime-space): Cleanup. + (slime-complete-restore-window-configuration): Use + slime-close-buffer instead of bury-buffer. + +2004-04-21 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * slime.el: Suppress byte-compiler warnings by binding + byte-compiler-warnings to nil. + (slime-repl-shortcut): Use a structure instead of a list for the + short cut info. Update the users accordingly. + + * swank-cmucl.lisp (arglist): Return a list instead of the string. + +2004-04-21 Edi Weitz <edi(a)agharta.de> + + * slime.el (slime-apropos): Add support for regexp-based apropos. + We use nregex, so the regexp syntax is different from Emacs' + regexps and bit restricted (alternation '|' and optional groups + '(xy)?' are not implemented). + (slime-insert-arglist): New command - stolen from ILISP. I always + thought this was quite useful. + (slime-oos): Fix typo. + + * swank.lisp (apropos-symbols): Use regexp and support + case-sensitive matching. + (arglist-for-echo-area): New argument to control if the operator + name should be included. + + * nregex.lisp: New file. + + * swank-loader.lisp (*sysdep-pathnames*): Load it. + +2004-04-21 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * doc/slime.texi (Compilation): slime-remove-notes is bound to C-c + M-c not M-c. Noted by Edi Weitz. + 2004-04-21 Edi Weitz <edi(a)agharta.de> * swank.lisp (list-all-package-names): Optionally include

1 0

[slime-devel] slime-insert-arglist
by Edi Weitz 21 Apr '04

21 Apr '04

OK, you got me hooked... :) Here's another idea - stolen from ILISP. I always thought this was quite useful. Cheers, Edi.

3 5

[slime-devel] slime-oos
by Edi Weitz 21 Apr '04

21 Apr '04

A typo, obviously.

2 1

Re: [slime-devel] slime-regex-apropos?
by Helmut Eller 21 Apr '04

21 Apr '04

Edi Weitz <edi(a)agharta.de> writes: > Anyway, what do you think about this? I think regex matching would be nice and consistent with Emacs' built in apropos. IMO, it would be more natural if we could do the filtering on the Lisp side. Perhaps we could include some of the lightweight regexp packages, like nregexp. nregexp is only 500 lines and the code can't be worse than the stuff in metering.lisp. Can find other uses for regexps as excuse to including it? Helmut.

3 3

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

21 Apr '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.339 slime/ChangeLog:1.341 --- slime/ChangeLog:1.339 Sat Apr 17 05:51:17 2004 +++ slime/ChangeLog Tue Apr 20 18:38:59 2004 @@ -1,3 +1,19 @@ +2004-04-21 Edi Weitz <edi(a)agharta.de> + + * swank.lisp (list-all-package-names): Optionally include + nicknames in the result. + + * slime.el (slime-read-package-name): Include nicknames in the + completions set. + (slime-repl-mode-map): Bind C-c : to slime-interactive-eval just + like in most other SLIME buffers. + (read-directory-name): Compatibilty defun. + +2004-04-20 Tiago Maduro-Dias <tcmd(a)rnl.ist.utl.pt> + + * slime.el (slime-close-buffer): New utility function. + (slime-space): Use it to kill superfluous *Completions* buffers. + 2004-04-17 Raymond Toy <rtoy(a)earthlink.net> * swank-cmucl.lisp (source-location-tlf-number)

1 0

Re: [slime-devel] list-all-package-names, really all... :)
by Helmut Eller 20 Apr '04

20 Apr '04

Edi Weitz <edi(a)agharta.de> writes: > Here's another tiny patch. It seems that the function > SWANK:LIST-ALL-PACKAGE-NAMES is only used for > slime-read-package-name. What about extending it such that nicknames > can also be entered? See below. Good idea. Patch applied. Helmut.

1 0