slime-devel September 2004

slime-devel@common-lisp.net

46 participants
71 discussions

[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

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

[slime-devel] Problems with LWW FLI
by Edi Weitz 29 Mar '05

29 Mar '05

Hi! Has anyone else problems with SLIME when using Lispworks on Windows (XP) and its FLI? I've run into a (reproducable but complicated) situation where SLIME simply hung while there were no problems from the LW IDE or from the command line. I'm sitting at my Linux laptop now but I can try to create a simple test case - I just wanted to check if this is a known problem. Cheers, Edi.

4 11

[slime-devel] eval-in-emacs and 'window'-debugger
by Antonio Menezes Leitao 10 Feb '05

10 Feb '05

Hi everybody, I noticed that slime provides a function eval-in-emacs that sends a form to the emacs side where it is evaluated. However, I would like to get the results on the lisp side but I always get NIL. Is there a different swank function for that? (in the emacs-lisp-interface from Franz I used a lep::eval-in-emacs that did precisely what I needed). This is very useful to provide refactoring operations (that operate on the Lisp side) that need to interact with the user using emacs lisp operations such as y-or-n-p or read-from-minibuffer. I know that it might be difficult to find a general scheme to translate from emacs lisp values to common lisp values but all I need is symbols, strings, numbers and such. ----------------- A few years ago I developed a 'window'-debugger and 'window'-inspector for Ilisp+CMUCL similar to what I used in the Explorer Lisp Machines. I recently adapted it to Slime+Whatever-Common-Lisp-slime-supports. If anyone is interested I can post it. However, I would like to suggest two changes to Slime in order to improve its portability: 1. The function swank::inspected-parts should provide a recognizable value for unbound slots. Here is one example in SBCL CL-USER> (defclass c () ((a))) #<STANDARD-CLASS C> CL-USER> (swank::inspected-parts (make-instance 'c)) "The object is a STANDARD-OBJECT of type C. " (("A" . #:INSPECT-UNBOUND-OBJECT-3530)) and in CLISP CL-USER> (swank::inspected-parts (make-instance 'c)) "#<COMMON-LISP-USER::C #x20426856> standard object type: COMMON-LISP-USER::C" (("A" . INSPECT-TMP-PACKAGE-5413::|#<unbound>|)) I know that the returned values are recognizable (e.g., by being the value of the variable sb-impl::*inspect-unbound-object-marker* or something similar) but given the fact that it depends on the Common Lisp being used, it would be preferable if Slime provided a function that recognizes such value. If it already does, my apologies. 2. The function swank::frame-locals doesn't distinguish valid locals from invalid ones. I know that not all Common Lisps make that distinction but for the ones that make, it would be useful to get that information (for Common Lisps that don't provide such information a default could be chosen). Currently, Slime puts a :not-available as value which, IMHO, is error-prone. It would be nicer to have an extra field for each local that describes its status or (as in 1.) a slime function that recognizes such special value or as a third (and not so good) alternative, swank::frame-locals should not produce invalid locals. Thanks in advance, António Leitão.

2 2

[slime-devel] Loading slime for clisp in xemacs on Windows
by Andrei Stebakov 23 Dec '04

23 Dec '04

Hi, I have xemacs and clisp that came with the cygwin distribution. I just downloaded slime-1.0 and put the following in my custom.el file: (add-to-list 'load-path "C:\\Linux\\slime-1.0\\") (add-hook 'lisp-mode-hook (lambda () (slime-mode t))) (add-hook 'inferior-lisp-mode-hook (lambda () (inferior-slime-mode t))) (setq inferior-lisp-program "clisp -K full") (require 'slime) (slime-setup) Now, when I load slime (via M-x slime) I got: [1]> *** - PARSE-NAMESTRING: syntax error in filename "c:\\Linux\\slime-1.0\\swank-loader.lisp" at position 2 Break 1 [2]> *** - READ from #<IO TERMINAL-STREAM>: there is no package with name "SWANK" Break 2 [3]> "C:\\DOCUME~1\\stebakov\\LOCALS~1\\Temp\\slime.2036" Break 2 [3]> Could anyone give me some info what I can do to fix it? Thanks, Andrei

5 9

[slime-devel] Debugger slowness is killing me ...
by Peter Seibel 07 Oct '04

07 Oct '04

I seem to keep doing things that drop me into the debugger with really long error messages. The amount of time it takes for the debugger to return (in Allegro anyway) seems to be proportional to the length of the output that has to be displayed in the *sldb* buffer. It can take many, many tens of seconds before the *sldb* shows up. In the meantime I have no idea what the heck is going on. To get a sense of what's happening try this: CL-USER> (defparameter *c* (make-condition 'simple-error :format-control "foo: ~a" :format-arguments (list (loop for i from 1 to 100000 collect i)))) *C* Then do this, hitting '0' as soon as you see the *sldb* buffer: CL-USER> (time (with-simple-restart (abort "Bail!") (error *c*))) I got: ; cpu time (non-gc) 750 msec user, 10 msec system ; cpu time (gc) 0 msec user, 0 msec system ; cpu time (total) 750 msec user, 10 msec system ; real time 8,289 msec ; space allocation: ; 805 cons cells, 2,463,904 other bytes, 0 static bytes NIL T The I redefined format-sldb-condition in swank-allegro.lisp from: (defimplementation format-sldb-condition (c) (princ-to-string c)) to this: (defimplementation format-sldb-condition (c) (let ((str (princ-to-string c))) (if (> (length str) 256) (format nil "~a ..." (subseq str 0 256)) str))) Now I try again: CL-USER> (time (with-simple-restart (abort "Bail!") (error *c*))) ; cpu time (non-gc) 630 msec user, 0 msec system ; cpu time (gc) 0 msec user, 0 msec system ; cpu time (total) 630 msec user, 0 msec system ; real time 1,102 msec ; space allocation: ; 756 cons cells, 1,269,984 other bytes, 0 static bytes NIL T ~8x faster. I don't think the condition is the only thing that matters. For instance the stack frames can also be quite long. (If you inline the call to MAKE-CONDITION rather than passing a parameter to ERROR it will also be quite slow, even with my change.) However I'm not sure if there's a good principled way to deal with this--it seems the ideal thing would be for SWANK to somehow keep more of the information on its side and send Emacs just enough to display the buffer while allowing emacs to request more information later. For example, we could stash the condition object somewhere on the connection and send emacs an abbreviated version. Then we could provide a keybinding in the *sldb* buffer that causes emacs to send a message to SWANK saying, send me the full condition now which would then be put in the appropriate place in the buffer. Or is that crazy? If not, if someone was feeling really ambitious, maybe this could be developed into a general facility--provide a way for SWANK to send emacs an object that contains a short string and an id which emacs can then use to request a more elaborate string representation. Then on the emacs side provide a function to insert such an object into a buffer with appropriate overlays or properties or whatever to make the short string "live" so clicking on it or hitting a key while the cursor is in it causes emacs to replace it with the longer version. -Peter -- Peter Seibel peter(a)javamonkey.com Lisp is the red pill. -- John Fraser, comp.lang.lisp

2 4

[slime-devel] Error loading slime - can't find easy-mode
by Dennis Dunn 01 Oct '04

01 Oct '04

Hello, I am using cygwin/clisp/xemacs21 with the cvs version of slime. I've added the forms to setup slime to my init.el file but when I start xemacs I get the following message in the mini-buffer: Error in init file: Cannot open load file: easy-mode I suspect that there is an emacs .el file that is usually distributed with emacs and/or xemacs that is not distributed with the cygwin version. Is there someplace where I can download the needed files or should I just can cygwin and use the native clisp/xemacs programs? Thanks for your time. --dennis

2 2

[slime-devel] edit-definition of *something*
by Alan Ruttenberg 29 Sep '04

29 Sep '04

Is it just me, or is it broken to edit definition on a symbol which has "*" at the end? It appears that the culprit is \> in the function-name regular expression in slime-goto-location-position. This is supposed to match a word break but according to M-x describe-syntax "*" is "symbol" as opposed to "word". I fixed it in my version by changing \\> to \\(\\>\\|\\s \\) but didn't want to put this into cvs before someone else commented. Should the syntax table be changed instead, or am I barking up the wrong tree? -Alan

2 1

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 29 Sep '04

29 Sep '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.540 slime/ChangeLog:1.541 --- slime/ChangeLog:1.540 Fri Sep 24 00:24:17 2004 +++ slime/ChangeLog Tue Sep 28 00:39:40 2004 @@ -1,3 +1,28 @@ +2004-09-27 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-process): New function intended to replace all + those references to the *inferior-lisp* buffer. + (slime-maybe-start-lisp): Split it up. + (slime-start-lisp): New function. + (slime-restart-inferior-lisp): Use the command from the existing + process to start the new process. + +2004-09-27 Christian Lynbech <christian(a)defun.dk> + + * slime.el (define-slime-dialect): New macro to make starting + Lisps with different command line options easier. + +2004-09-27 Rui Patrocínio <rui.patrocinio(a)netvisao.pt> + + * swank.lisp (mop, mop-helper): Support functions for the class + browser. + + * slime.el (slime-browse-classes, slime-browse-xrefs): New + commands to browse class hierarchies and xref graphs in a tree + widget. + + * tree-widget.el: New file. Only needed for older Emacsen. + 2004-09-23 Helmut Eller <heller(a)common-lisp.net> * slime.el (slime-start-and-load): Take arguments so that the

1 0

[slime-devel] 3 todo's
by Tiago Maduro-Dias 28 Sep '04

28 Sep '04

Hi! I've recently started using slime again and I was pleasantly surprised with the obvious evolution! There were a few things that caught my eye though: 1. In APROPOS, multi-line documentation strings don't show properly (only the first line is shown). 2. I really miss a function which would be able to restore the previous window state after using apropos and such. This is a bit more difficult to specify. I was hoping for something like: "whenever a certain type of buffer comes into play due to a function call (e.g., slime-apropos brings up the *SLIME Apropos* buffer), the window state is saved and is retrievable by a call to slime-recover-window-state (or something of the sort). While such class of buffers are shown, no window state is saved again." This is annoying because I spend some time organizing my buffers and then a call to apropos just messes everything up. 3. I'm using Allegro CL 6.2. One thing allegro does is provide a reference character near the place where a given error/warning occurred. Isn't it possible to use this information in the compilation notes buffer? So that one can access the place of the error via a single click as is possible with sbcl for instance? I hope my english was clear enough :). Thank you for your time, Tiago Maduro-Dias.

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel September 2004