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

[slime-devel] slime-apropos-package now sorts correctly
by Hoehle, Joerg-Cyril 20 Apr '07

20 Apr '07

Hi, slime-apropos-package now conforms to its specification and also sorts symbols printed with package prefix. I supply the patches as attachments in the hope that MS-Windows nor MS-Outlook will break the TAB and LF characters of the original diff. I hope this is fine. Regards, Jörg Höhle.

3 3

[slime-devel] slime-display-edit-hilights
by Marco Baringer 23 Dec '06

23 Dec '06

for those of you who don't follow c.l.l (which is probaly a good idea) i commited William Bland's patch[1]. see the ChangeLog for details. 1 - http://groups.google.com/group/comp.lang.lisp/browse_thread/thread/e1d0b7bf… -- -Marco Ring the bells that still can ring. Forget the perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen

8 20

[slime-devel] [patch] closing connections with :fd-handler style
by Stephen Compall 15 Mar '06

15 Mar '06

As far as I can tell, the only way a Swank connection object with style :fd-handler will ever be closed due to EOF (with close-connection) is if either the fd-handler implementation detects the EOF state and knows how to destroy Swank connections, or a condition is raised in the dynamic context of with-reader-error-handler. Looking at the topmost form in that context, however, it can only happen if (listen socket) answers T, so that the attempt to read can proceed and raise an eof-error, which gets wrapped up, etc. I modified process-available-input to test (listen socket) only after calling FN at least once; after all, it always returns T when the handler is called for a normal input state. Without this patch, my fd-handler backend gets into an endless loop calling the handler in install-fd-handler (with the :eof state); with this patch, the socket is closed, removed from *connections*, and from the fd-handler backend properly. Attached is the patch. -- Stephen Compall http://scompall.nocandysoftware.com/blog

2 4

[slime-devel] Odd bug - heads up
by Alan Ruttenberg 15 Mar '06

15 Mar '06

I found that presentations which were in my repl input history, weren't being recalled as presentations when I recalled previous history - they were coming back as text, and so would generally trigger a reader error when I tried the command. I tracked this down to (defun slime-repl-replace-input (string) (slime-repl-delete-current-input) (setq it string) (insert-and-inherit string)) If one uses insert, instead of insert-and-inherit then repl history works correctly for presentations, for me. No idea why this is problematic. It looks like this function has been this way for a long time - perhaps a bug in the emacs I am using (OS X tiger, fink installed, I think). Anyways, thought I'd post this in case anyone else was having the same problem, or had some insight as to why this is happening. -Alan

2 1

[slime-devel] patch: make slime-echo-arglist show initargs/initforms for make-instance
by Luís Oliveira 06 Feb '06

06 Feb '06

Hello, The attached patch makes slime-echo-arglist detect (make-instance 'quoted-symbol ...) forms and uses the quoted symbol to find the class and present the initargs and initforms in the mini-buffer. For example: CL-USER> (defclass foo () ((a :initarg :initarg-a :initform nil) (b :initarg :initarg-b) c)) #<STANDARD-CLASS FOO> CL-USER> (make-instance<space> ;; minibuffer displays: (make-instance class &rest initargs) CL-USER> (make-instance 'foo<space> ;; minibuffer displays: (make-instance 'foo &key (initarg-a nil) initarg-b) The code is a bit ugly, specially on the elisp side. My elisp-fu being very weak doesn't help. Suggestions on how to improve that are most welcome! BTW, the ChangeLog's encoding seems to be latin-1, wouldn't utf-8 be better? -- Luís Oliveira luismbo (@) gmail (.) com Equipa Portuguesa do Translation Project http://www.iro.umontreal.ca/translation/registry.cgi?team=pt

2 3

[slime-devel] Slime will not start on Fedora with CLISP
by stephen.3.odonnell＠bt.com 02 Feb '06

02 Feb '06

Guys, I am totally new to Lisp, but am trying to learn, however I cannot get slime to install on my linux box! I want to be able to use slime with clisp using emacs from the command line (ie in a terminal window as oppose to in a GUI). I have tried both the latest version from CVS and the stable released version, but both give the same error. My .emacs entry and output when slime attempts to start are below. Any help would be much appreciated! emacs entry:- (setq inferior-lisp-program "clisp") (add-to-list 'load-path "/home/sodonnel/slime/slime") (require 'slime) (slime-setup) Startup output:- (load "/home/sodonnel/slime/slime/swank-loader.lisp" :verbose t) (swank:start-server "/tmp/slime.12088" :external-format :iso-latin-1-unix) i i i i i i i ooooo o ooooooo ooooo ooooo I I I I I I I 8 8 8 8 8 o 8 8 I \ `+' / I 8 8 8 8 8 8 \ `-+-' / 8 8 8 ooooo 8oooo `-__|__-' 8 8 8 8 8 | 8 o 8 8 o 8 8 ------+------ ooooo 8oooooo ooo8ooo ooooo 8 Copyright (c) Bruno Haible, Michael Stoll 1992, 1993 Copyright (c) Bruno Haible, Marcus Daniels 1994-1997 Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold 1998 Copyright (c) Bruno Haible, Sam Steingold 1999-2000 Copyright (c) Sam Steingold, Bruno Haible 2001-2006 [1]> ;; Loading file /home/sodonnel/slime/slime/swank-loader.lisp ... ;; Loading file /home/sodonnel/.slime/fasl/clisp-2.38-unix-pc386/swank-backend\ .fas ... ;; Loaded file /home/sodonnel/.slime/fasl/clisp-2.38-unix-pc386/swank-backend.\ fas ;; Loading file /home/sodonnel/.slime/fasl/clisp-2.38-unix-pc386/nregex.fas ..\ . ;; Loaded file /home/sodonnel/.slime/fasl/clisp-2.38-unix-pc386/nregex.fas ;; Loading file /home/sodonnel/.slime/fasl/clisp-2.38-unix-pc386/xref.fas ... ;; Loaded file /home/sodonnel/.slime/fasl/clisp-2.38-unix-pc386/xref.fas ;; Loading file /home/sodonnel/.slime/fasl/clisp-2.38-unix-pc386/metering.fas \ ... ;; Loaded file /home/sodonnel/.slime/fasl/clisp-2.38-unix-pc386/metering.fas ;; Loading file /home/sodonnel/.slime/fasl/clisp-2.38-unix-pc386/swank-clisp.f\ as ... WARNING: Replacing method #<STANDARD-METHOD (#<BUILT-IN-CLASS T>)> in #<STANDARD-GENERIC-FUNCTION CALL-WITHOUT-INTERRUPTS> WARNING: Replacing method #<STANDARD-METHOD NIL> in #<STANDARD-GENERIC-FUNCTION LISP-IMPLEMENTATION-TYPE-NAME> WARNING: Replacing method #<STANDARD-METHOD (#<BUILT-IN-CLASS T>)> in #<STANDARD-GENERIC-FUNCTION SET-DEFAULT-DIRECTORY> WARNING: Replacing method #<STANDARD-METHOD (#<BUILT-IN-CLASS T>)> in #<STANDARD-GENERIC-FUNCTION ARGLIST> *** - READ: input stream #<INPUT BUFFERED FILE-STREAM CHARACTER #P"/home/sodonnel/.slime/fasl/clisp-2.38-unix-pc386/swank-clisp.fas" @408> ends within a token after multiple escape character The following restarts are available: SKIP :R1 skip (LOAD-SWANK) STOP :R2 stop loading file /home/sodonnel/slime/slime/swank-load\ er.lisp ABORT :R3 ABORT Break 1 SWANK-BACKEND[2]>

2 1

[slime-devel] Problem installing slime (fedora core 4/clisp)
by stephen.3.odonnell＠bt.com 01 Feb '06

01 Feb '06

Guys, I am totally new to Lisp, but am trying to learn, however I cannot get slime to install on my linux box! I want to be able to use slime with clisp using emacs from the command line (ie in a terminal window as oppose to in a GUI). I have tried both the latest version from CVS and the stable released version, but both give the same error. My .emacs entry and output when slime attempts to start are below. Any help would be much appreciated! emacs entry:- (setq inferior-lisp-program "clisp") (add-to-list 'load-path "/home/sodonnel/slime/slime") (require 'slime) (slime-setup) Startup output:- (load "/home/sodonnel/slime/slime/swank-loader.lisp" :verbose t) (swank:start-server "/tmp/slime.12088" :external-format :iso-latin-1-unix) i i i i i i i ooooo o ooooooo ooooo ooooo I I I I I I I 8 8 8 8 8 o 8 8 I \ `+' / I 8 8 8 8 8 8 \ `-+-' / 8 8 8 ooooo 8oooo `-__|__-' 8 8 8 8 8 | 8 o 8 8 o 8 8 ------+------ ooooo 8oooooo ooo8ooo ooooo 8 Copyright (c) Bruno Haible, Michael Stoll 1992, 1993 Copyright (c) Bruno Haible, Marcus Daniels 1994-1997 Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold 1998 Copyright (c) Bruno Haible, Sam Steingold 1999-2000 Copyright (c) Sam Steingold, Bruno Haible 2001-2006 [1]> ;; Loading file /home/sodonnel/slime/slime/swank-loader.lisp ... ;; Loading file /home/sodonnel/.slime/fasl/clisp-2.38-unix-pc386/swank-backend\ .fas ... ;; Loaded file /home/sodonnel/.slime/fasl/clisp-2.38-unix-pc386/swank-backend.\ fas ;; Loading file /home/sodonnel/.slime/fasl/clisp-2.38-unix-pc386/nregex.fas ..\ . ;; Loaded file /home/sodonnel/.slime/fasl/clisp-2.38-unix-pc386/nregex.fas ;; Loading file /home/sodonnel/.slime/fasl/clisp-2.38-unix-pc386/xref.fas ... ;; Loaded file /home/sodonnel/.slime/fasl/clisp-2.38-unix-pc386/xref.fas ;; Loading file /home/sodonnel/.slime/fasl/clisp-2.38-unix-pc386/metering.fas \ ... ;; Loaded file /home/sodonnel/.slime/fasl/clisp-2.38-unix-pc386/metering.fas ;; Loading file /home/sodonnel/.slime/fasl/clisp-2.38-unix-pc386/swank-clisp.f\ as ... WARNING: Replacing method #<STANDARD-METHOD (#<BUILT-IN-CLASS T>)> in #<STANDARD-GENERIC-FUNCTION CALL-WITHOUT-INTERRUPTS> WARNING: Replacing method #<STANDARD-METHOD NIL> in #<STANDARD-GENERIC-FUNCTION LISP-IMPLEMENTATION-TYPE-NAME> WARNING: Replacing method #<STANDARD-METHOD (#<BUILT-IN-CLASS T>)> in #<STANDARD-GENERIC-FUNCTION SET-DEFAULT-DIRECTORY> WARNING: Replacing method #<STANDARD-METHOD (#<BUILT-IN-CLASS T>)> in #<STANDARD-GENERIC-FUNCTION ARGLIST> *** - READ: input stream #<INPUT BUFFERED FILE-STREAM CHARACTER #P"/home/sodonnel/.slime/fasl/clisp-2.38-unix-pc386/swank-clisp.fas" @408> ends within a token after multiple escape character The following restarts are available: SKIP :R1 skip (LOAD-SWANK) STOP :R2 stop loading file /home/sodonnel/slime/slime/swank-load\ er.lisp ABORT :R3 ABORT Break 1 SWANK-BACKEND[2]>

2 1

[slime-devel] potentially harmful bug when restarting SLIME
by Bradford W Miller 31 Jan '06

31 Jan '06

I'm a new user of SLIME; built from CVS, and am using emacs (fink) 21.3.50.1 under X, and Lispworks (Pro) on Mac. Startup slime note that the *SLIME-Typeout* screen appears (separately), read in some buffers. Kill slime (m-x slime-quit-lisp). Delete the buffer *Slime-Typeout* which is then replaced by some other buffer Emacs has, probably one of your source code buffers. Restart slime. Any output slime would direct to the *SLIME-Typeout* window is now directed to the exposed buffer in the mini-screen instead. Accidentally saving this file could lead to lost work. (for instance, in the REPL, type "(defun " to get a prompt for the arguments to defun). Thanks, Bradford Miller Cognitive/Computer Scientist Have Mind, Will Model Work: 401.842-3578 Fax: 401.842-2040 Email: <mailto:Bradford_W_Miller@Raytheon.com> Bradford_W_Miller(a)Raytheon.com Professional <https://www.linkedin.com/e/fps/1075898/> Profile <http://www.raytheon.com> Raytheon, IDS <http://maps.google.com/maps?q=Naval+Integration+Center%2C1847+West+Main+R oad%2C+N19%2CPortsmouth%2CRhode+Island+02871&hl=en> Naval Integration Center 1847 West Main Road, N19 Portsmouth, Rhode Island 02871 See who we know in common <https://www.linkedin.com/e/wwk/1075898/> Want a signature <https://www.linkedin.com/e/sig/1075898/> like this?

1 0

[slime-devel] Slime support for metaclasses
by Ian Eslick 31 Jan '06

31 Jan '06

Slime's default inspector won't show slot values for metaclasses that override the default storage locations for objects slots (i.e. where the default slot-boundp returns nil). The elephant interface to Berkeley-DB is one such system. The (defmethod inspect-for-emacs ((o standard-object) inspector) (declare (ignore inspector)) (values "An object." `("Class: " (:value ,(class-of o)) (:newline) "Slots:" (:newline) ,@(loop for slot in (swank-mop:class-slots (class-of o)) for slot-def = (find-effective-slot o slot) for slot-name = (swank-mop:slot-definition-name slot-def) collect `(:value ,slot-def ,(string slot-name)) collect " = " collect (if (swank-mop:slot-boundp-using-class (class-of o) o slot) `(:value ,(swank-mop:slot-value-using-class (class-of o) o slot-def)) "#<unbound>") collect '(:newline))))) If you add the two calls to slot-boundp-using-class and slot-value-using-class as shown above you get the expected proper behavior for lisps that don't call the -using-class mop functions from the slot-value and slot-boundp functions. (I ran into this on Allegro 7.0 under Mac OS X). The other change is to add these two functions to the swank-mop package exports. It's a minor enough change I figured someone who checks in regularly can update this and provide some judgement on whether there are likely to be any problems. Regards, Ian

4 5

[slime-devel] Problems downloading SLIME
by David Novogrodsky 31 Jan '06

31 Jan '06

I have tried several times to download SLIME from this web site: http://common-lisp.net/project/slime/ Without success. Keep getting zero header error. How do I access CVS using a terminal. I tried cutting and pasdting the commands on the above html page but did not work. Thanks.

3 2

[slime-devel] Slime support for metaclasses...
by Pascal Costanza 31 Jan '06

31 Jan '06

Hi, I have seen a discussion on slot-boundp / slot-makunbound and their MOP counterparts. I have tried to respond, but wasn't subscribed to this mailing list yet. This time I should get through... Most CLOS MOP implementations indeed specialize the third arguments in the slot-xxx-using-class generic functions on slot definition metaobjects. There are two exceptions (one is well known, the other probably not so much): - LispWorks specializes on slot names. This is probably because the switch from slot names to slot definition metaobjects in the slot-xxx- using-class functions was a very late change in the CLOS MOP specification, and the LispWorks CLOS implementation seems to be based on some older version of PCL (?!?). - Allegro specializes slot-value-using-class and (setf slot-value- using-class) on slot definition metaobjects, BUT specializes slot- boundp-using-class and slot-makunbound-using-class on slot names!!! This is not documented anywhere, so it's probably a source of confusion. (I have only accidentally found out about this. I have already filed a bug report with Franz.) I don't know exactly the context of your discussion, but you could use the Closer to MOP compatibility layer which fixes the slot-xxx- using-class functions for LispWorks and Allegro so that all slot-xxx- using-class functions are specialized on slot definition metaobjects. However, this may have other drawbacks that I cannot judge from here... Cheers, Pascal -- Pascal Costanza, mailto:pc@p-cos.net, http://p-cos.net Vrije Universiteit Brussel, Programming Technology Lab Pleinlaan 2, B-1050 Brussel, Belgium

1 0

[slime-devel] comma shortcut doesn't work always
by Edi Weitz 31 Jan '06

31 Jan '06

Another minor glitch that I encountered is that the comma shortcut in the REPL doesn't always work. I can consistently reproduce it (GNU Emacs 21.3.50 and also 21.3 release) like this: 1. Make sure point is at the beginning of a REPL input line. 2. Split Emacs frame into two windows, one of them being the REPL the other one containing something else. 3. Hide REPL window with C-x 0. 4. Now type M-x slime. 5. Type the comma. At this point I'm not asked for a shortcut command in the minibuffer but the comma is simply entered into the REPL instead. Anybody else seeing this? Cheers, Edi.

10 25

[slime-devel] patch: show initargs/initforms in slime-echo-arglist
by Luís Oliveira 30 Jan '06

30 Jan '06

Hello, The attached patch extends slime-echo-arglist in order to display a classe's initargs and initforms when make-instance is detected. Here's an example: CL-USER> (defclass foo () ((a :initarg :initarg-a :initform nil) (b :initarg :initarg-b) c)) #<STANDARD-CLASS FOO> CL-USER> (make-instance<space> ;; minibuffer displays: (make-instance class &rest initargs) CL-USER> (make-instance 'foo<space> ;; minibuffer displays: (make-instance 'foo &key (initarg-a nil) initarg-b) The code is a bit ugly, specially on the elisp side. It could perhaps be generalized to support more cases like this. Suggestions on how to improve it are most welcome! (BTW, the ChangeLog seems to be use the latin-1 enconding, perhaps using utf-8 and/or adding a -*- coding: ... -*- line at the top would be a good idea?) -- Luís Oliveira luismbo (@) gmail (.) com Equipa Portuguesa do Translation Project http://www.iro.umontreal.ca/translation/registry.cgi?team=pt

2 2

[slime-devel] slime fails to start after Linux upgrade
by John Whittaker 30 Jan '06

30 Jan '06

I recently upgraded my Mandriva Linux system after reading about some KDE security flaw. I shouldn't have done it, but it's too late now. Among other problems, I now cannot run slime and cmucl from xemacs. I get the following error message: 'itimer "run-with-timer" signaled: (error "127.0.0.1/x^T-^H& Servname not supported for ai_socktype")' This behavior was the same for my old slime setup, which was 1.2.1, and my current which is the latest tarball from common-lisp.net. Does anyone have any idea what is causing this and how I can fix it? Thanks, John Whittaker

1 0

[slime-devel] Making potentially problematic changes
by Ian Eslick 27 Jan '06

27 Jan '06

I've updated the inspector in swank.lisp to support metaclass based slot-value overrides. This requires use of the mop functions slot-boundp-using-class and slot-value-using-class (and adding them to the swank-mop package) which may not be consistent over the various versions. Since the inspector is rather central to slime, I don't want to commit this change directly (and don't have write permissions to slime CVS (ieslick(a)common-lisp.net) Is there a proper procedure for testing a change like this if you don't have all the test configurations available locally? Thank you, Ian

2 1

[slime-devel] newbie REPL questions
by funkyj＠gmail.com 24 Jan '06

24 Jan '06

I'm not sure how the whole SLIME development cycle is suppose to work. One of the things that is confusing me is that selecting various options in SLDB causes the REPL to lose its connection with the inferior lisp, requiring me to do 'M-x slime' to reconnect. Here is an example: ;; starting slime for the first time in this emacs session M-x slime ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; messages Connecting to Swank on port 2369.. Process bridge is installed Connected. Hack and be merry! ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; repl buffer shows ; SLIME 2006-01-20 CL-USER> x ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; sldb clisp/0 buffer appears EVAL: variable X has no value [Condition of type SYSTEM::SIMPLE-UNBOUND-VARIABLE] Restarts: 0: [USE-VALUE] You may input a value to be used instead of X. 1: [STORE-VALUE] You may input a new value for X. 2: [ABORT-REQUEST] Abort handling SLIME request. 3: [ABORT] ABORT Backtrace: 0: #<SYSTEM-FUNCTION EVAL> 1: #<COMPILED-FUNCTION SWANK::EVAL-REGION> 2: #<COMPILED-FUNCTION SWANK::LISTENER-EVAL-1> 3: #<COMPILED-FUNCTION #:|273 275 (DEFINTERFACE CALL-WITH-SYNTAX-HOOKS (FN) ...)-31-3-1-1|> 4: #<COMPILED-FUNCTION SWANK::CALL-WITH-BUFFER-SYNTAX> 5: #<COMPILED-FUNCTION SWANK:LISTENER-EVAL> 6: #<SYSTEM-FUNCTION EVAL> 7: #<COMPILED-FUNCTION SWANK::EVAL-FOR-EMACS-1> 8: #<COMPILED-FUNCTION #:|472 477 (DEFINTERFACE CALL-WITH-DEBUGGER-HOOK (HOOK FUN) ...)-52-3-1-1|> 9: #<COMPILED-FUNCTION SWANK::EVAL-FOR-EMACS> 10: #<COMPILED-FUNCTION SWANK::READ-FROM-EMACS> 11: #<COMPILED-FUNCTION SWANK::HANDLE-REQUEST-1> 12: #<COMPILED-FUNCTION #:|472 477 (DEFINTERFACE CALL-WITH-DEBUGGER-HOOK (HOOK FUN) ...)-52-3-1-1|> 13: #<COMPILED-FUNCTION SWANK::CALL-WITH-CONNECTION-1> 14: #<COMPILED-FUNCTION SWANK::CALL-WITH-REDIRECTED-IO> 15: #<COMPILED-FUNCTION SWANK::MAYBE-CALL-WITH-IO-REDIRECTION> 16: #<COMPILED-FUNCTION SWANK::CALL-WITH-CONNECTION> 17: #<COMPILED-FUNCTION SWANK::HANDLE-REQUEST> 18: #<COMPILED-FUNCTION SWANK::SIMPLE-SERVE-REQUESTS-2> 19: #<COMPILED-FUNCTION SWANK::SIMPLE-SERVE-REQUESTS> 20: #<COMPILED-FUNCTION SWANK::SERVE-REQUESTS> 21: #<COMPILED-FUNCTION SWANK::SERVE-CONNECTION> 22: #<COMPILED-FUNCTION SWANK::SETUP-SERVER-SERVE> 23: #<COMPILED-FUNCTION SWANK::SETUP-SERVER> 24: #<COMPILED-FUNCTION SWANK:START-SERVER> 25: #<SYSTEM-FUNCTION SYSTEM::READ-EVAL-PRINT> 2 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; type '3' (abort) into the sldb buffer ;; the following minibuffer message appears: Lisp connection closed unexpectedly: exited abnormally with code 256 ;; type 'enter' in repl buf and I see: if: Not connected. Use `M-x slime' to start a Lisp. ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; Starting slime again with M-x slime works fine but takes a long ;; time. It seems a lot of actions cause the lisp connection to close unexpectedly. Is this normal? Should I just ignore it and restart slime? Restarting slime after each "mistake" (I make a lot of them) is rather tedious. FYI: I'm using clisp from cygwin: GNU CLISP 2.35 (2005-08-29) (built on winsteingoldlap.ad.alphatech.com [10.41.52.182]) Software: GNU C 3.4.4 (cygming special) (gdc 0.12, using dmd 0.125) gcc -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -O2 -fexpensive-optimizations -DUNICODE -DDYNAMIC_FFI -I. -x none -lintl libcharset.a libavcall.a libcallback.a -lreadline -lncurses -liconv -L/usr/local/libsigsegv-cygwin/lib -lsigsegv -L/usr/X11R6/lib -lX11 SAFETY=0 HEAPCODES STANDARD_HEAPCODES SPVW_PAGES SPVW_MIXED libsigsegv 2.2 libiconv 1.9 Features: (REGEXP SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL COMMON-LISP LISP=CL INTERPRETER SOCKETS GENERIC-STREAMS LOGICAL-PATHNAMES SCREEN FFI GETTEXT UNICODE BASE-CHAR=CHARACTER PC386 UNIX CYGWIN) C Modules: (clisp i18n syscalls regexp) Installation directory: /usr/lib/clisp/ User language: ENGLISH Machine: I686 (I686) jcano-lt.jnpr.net [192.168.1.103] and GNU Emacs 21.3.1 (i386-mingw-nt5.1.2600) of 2004-03-10 on NYAUMO SLIME, as you can see is the CVS head I checked out 2006-01-20. Thanks in advance, --jfc

2 2

[slime-devel] shortcuts to OPs other than ASDF's own
by Walter C. Pelissero 24 Jan '06

24 Jan '06

I was wondering if this patch could be considered for inclusion in SLIME. It allows to write repl shortcuts for operations not belonging to the ASDF package simply prefixing the operation string with the package name. diff -c -r1.92 swank-backend.lisp *** swank-backend.lisp 23 Oct 2005 08:47:54 -0000 1.92 --- swank-backend.lisp 24 Jan 2006 13:51:45 -0000 *************** *** 313,319 **** (error "ASDF is not loaded.")) (with-compilation-hooks () (let ((operate (find-symbol "OPERATE" :asdf)) ! (operation (find-symbol operation-name :asdf))) (when (null operation) (error "Couldn't find ASDF operation ~S" operation-name)) (apply operate operation system-name keyword-args)))) --- 313,323 ---- (error "ASDF is not loaded.")) (with-compilation-hooks () (let ((operate (find-symbol "OPERATE" :asdf)) ! (operation (let ((colon (position #\: operation-name))) ! (if colon ! (find-symbol (subseq operation-name (1+ colon)) ! (subseq operation-name 0 colon)) ! (find-symbol operation-name :asdf))))) (when (null operation) (error "Couldn't find ASDF operation ~S" operation-name)) (apply operate operation system-name keyword-args)))) -- walter pelissero http://www.pelissero.de

1 0

[slime-devel] New startup behavior
by Jonathon McKitrick 24 Jan '06

24 Jan '06

Hi all, I noticed that since the recent change in startup behavior, slime seems to compile a lot more code each time it is started. My older laptop takes a lot longer to start than before, when sbcl used asdf to load it, IIRC. Is there a way to avoid this delay with each start? -Jonathon -- "I am sure that Jesus would use a command prompt. Hello? Ten Commandments??"

1 0

[slime-devel] SLIME and CLX and CMUCL "lock up" problem
by David Trudgett 24 Jan '06

24 Jan '06

Hi everyone, I was directed to this mailing list by a fellow on comp.lang.lisp, so hopefully this is the right place to ask. I've been using SLIME for a while now (I'm just a Lisp newbie, however), and it has been really great. Since doing some CLX programming in CMUCL, I've noticed a lot of "freeze ups" where the Lisp subprocess just goes off and does its own thing and has to be sent a TERM signal, which means I also have to restart SLIME. Is this a known conflict between the CLX library and SLIME? If any of you guys has a suggestion about how I might work around this, or ideas about what else might be causing problems, it would be greatly appreciated. My environment is: GNU Emacs 21.4.1 SLIME 2005-12-27 (from CVS) CMUCL 19a CLX X Library MIT R5.02, (the one that comes with CMUCL) Thanks for doing a great job with SLIME! Bye for now, David -- David Trudgett http://www.zeta.org.au/~wpower/ Hickory Dickory Dock, The mice ran up the clock, The clock struck one, The others escaped with minor injuries.

1 0

[slime-devel] [Feature Request:] keeping history for several macroexpansions in a row
by Tobias C. Rittweiler 23 Jan '06

23 Jan '06

Hi Slime-hackers, I'd like to suggest keeping a stack-like history for several macroexpansions in a row such that you can easily go back one macroexpansion after you've macroexpanded a form /inside/ the macroexpansion buffer. Erm, yeah, sure, here's a small example: Let's say you have two macros like these: (defmacro with-foo (() &body body) `(flet ((foo (arg) arg)) ,@body)) (defmacro with-bar ((arg) &body body) `(with-foo () (prog1 (foo ,arg) ,@body))) Ah, well, hopefully yours will do something less stupid. Anyway, let's further say that you want to macroexpand (`C-c RET') the following form: (with-bar ('foobar) (let ((x 1)) (* x x))) the macroexpansion buffer should pop up containing something like (WITH-FOO NIL (PROG1 (FOO 'FOOBAR) (LET ((X 1)) (* X X)))) Now you want to expand that form as well, so you place point before `(WITH-FOO' and press `C-c RET' again, now the old expansion buffer disappears and instead a new one pops up in some other window. While it's cool that macroexpansion works from within the macroexpansion buffer, the current behaviour is unfortunately somewhat annoying, because upon exit from the expansion buffer (via pressing `q'), -- while the old buffer constellation is nicely recovered as of before any macroexpansion --, the point won't afterwards be in the same window where you started macroexpansion. (Split your emacs horizentally, on top the REPL, on the bottom the slime-scratch buffer; now paste the above form in the REPL and do a macroexpansion there, slime-scratch will be replaced by the expansion buffer; now expand again from inside the macroexpansion buffer, a new expansion buffer will be placed into the REPL window; there press `q' and the point will be within slime-scratch although you started from the REPL.) I suggest a slightly different behaviour when expanding a form from within the macroexpansion buffer: the old buffer should be reused and you should be able to go back to the previous macroexpansion (like what `l' does in the inspector.) Additionally I'd like to suggest a way to macroexpand into a newly created macroexpansion buffer that's independant from a possibly other expansion buffer that got created prior. The purpose is simply for side-by-side comparasions of the same macro but that was modified in between. Finally, I'm often hit by not releasing the control-key fast enough such that a `C-c C-RET' key sequence is generated. Maybe that could be made an alias for `C-c RET'? Keep up the great work! -*- tcr

2 1

[slime-devel] Auto-nag: slime link verifier failed
by root＠common-lisp.net 23 Jan '06

23 Jan '06

You are being nagged on because your project's name showed up in the nightly Checkbot run. Checkbot checks for broken links etc. This probably means that you are either pointing to a broken link or that someone is pointing to a broken link on your site. Or something else, it check's a bunch of stuff. Update your webpages or you shall be nagged again next week. To find out what's wrong with your webpages, please consult: http://common-lisp.net/checkbot/checkbot-common-lisp.net.html Any questions? You can reach the author of this cronjob at clo-devel(a)common-lisp.net Thanks!

1 0

[slime-devel] CVS version can't find swank?
by Jonathon McKitrick 21 Jan '06

21 Jan '06

I *just* updated from cvs and now sbcl and slime cannot find swank. (require 'swank) returns nil, and swank:create-server fails of course. Any ideas? -Jonathon -- "I am sure that Jesus would use a command prompt. Hello? Ten Commandments??"

4 7

Re: [slime-devel] clisp without unicode patch
by Hoehle, Joerg-Cyril 21 Jan '06

21 Jan '06

Helmut Eller wrote: >The user has to choose an encoding that actually works I had hoped for auto-detection, or at least reasonable defaults and consistent settings. E.g. I found a message in the *inferior-lisp* buffer ("event-history end") saying that iso-8859-1 was used. However, the buffer's mode line says "u". Same for the slime-repl and *slime-events* buffers. Same for many other buffers in Emacs (e.g. Dired), while Lisp source buffers mostly say "--", i.e. ASCII. .slime-history.eld says -*- utf-8-unix (but so far there's only ASCII therein). This is Emacs-21.4 on a Ubuntu Breezy i386 with the default clisp-2.35 (not self compiled) -- with #+UNICODE. How comes? Is that 1/3 a bug-report? >because the packet length field isn't interpreted >correctly and the payload of the packet will be truncated I wasn't aware slime is sending packets. I thought it's all Lisp data, readable with READ :) I think it's then ok to modify the patch to assert :iso-8859-1 on a non unicode clisp. And let the user figure out how to set this??? Regards, Jorg Hohle.

3 2

Re: [slime-devel] Re: CLISP SLIME implementation breaks in CVS
by Bill_Clementson＠peoplesoft.com 21 Jan '06

21 Jan '06

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 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] > > I can reproduce this but I've no idea what is causing it. It /looks/ > like someone is trying to call defslimefun as a function rather than a > macro, but I don't see where it could happen -- the macro is declared > at the top of the only file that refers to it. > > I did fix a different but similar problem that I got under CLISP. It > seems like I had to swap the order of a couple of macros, one of which > expanded into into code that calls the other, but that surely can't be > the reason. > > > Backtrace: > > 0: EVAL frame for form (SWANK:CREATE-SWANK-SERVER 4007) > > Mine actually gives an empty backtrace (!). I fixed the Elisp-side to > handle that incase it helps someone more CLISP-savvy find the problem. Has anybody had any luck in finding the source of this problem? CLISP still breaks for me in the latest CVS. I have had a look at all of the DEFSLIMEFUN's that were modified since 4/18 (the previous CVS version that I had which was working ok with CLISP) and haven't found any obvious clues. Any suggestions on how I might debug this issue as it occurs at startup during the slime-connect processing in Emacs (after CLISP has started up successfully)? - Bill

5 6

Re: [slime-devel] Re: SBCL restart-frame
by Mészáros Levente 20 Jan '06

20 Jan '06

> levy> On the other hand return from frame is already supported for SBCL > in > levy> SLIME. > > levy> And if I got it right the above statement also means that return > from > levy> frame works the same "somewhat bad" way. I mean returning from the > levy> frame of bar (in the debugger) the value of *a* will return 1 > instead of > levy> 0. > > levy> Am I right? > > Yes. However, there are two environments here: > > 1) The environment used to compute arguments for the command. Possibly > this > should be the environment of the frame, but it doesn't matter too much > as > long as the person debugging the code knows which environment is used. > > 2) The environment used to execute the command. For "restart frame", this > should be the original environment of the frame, otherwise functions > like > FOO will fail to perform correctly. For "return from frame" it doesn't > really matter which environment is used, becase no user code is > executed. > > __Martin I see your points, but the last statement I think is not quite true. Return from the frame can evaluate an expression which might or might not refer to user code. Actually it is very usefull to call the original function with different parameters for example. In which case the environment problem still exists. Of course if one is aware of that then the issue can be safely avoided. levy ________________________________________________________________ Elégedetlen helyzetével? Új kihívásokra vágyik? Állást Keres? - Mi segítünk! www.jobpilot.hu

2 1