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

[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] Arglist while in SLIME debugger
by Lynn Quam 28 Jan '05

28 Jan '05

I find it somewhat annoying that I cannot see the arglist information for functions while in the SLIME debugger. Is it possible to change SLIME-BUSY-P so that SLIME-AUTODOC-MODE and SLIME-SPACE will continue to work while inside the SLIME debugger? To implement this, the SLIME-BUSY-P needs to know the rex-continuations for the forms that cause the debugger to be entered. The SLIME debugger needs to be able to figure out the rex-continuation of the form that caused the debugger to be entered and add it to the list in the global variable *SLDB-REX-CONTINUATIONS*. When the debugger exits, it needs to remove it from the list. SLIME-BUSY-P would become something like: (defvar *sldb-rex-continuations* nil) (defun slime-busy-p () "True if Lisp has outstanding requests." (let ((sldb-continuations *sldb-rex-continuations*)) (dolist (contin (slime-rex-continuations) nil) (if (not (memq contin sldb-continuations)) (return t)))))

2 3

[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] how to interrupt & kill function execution
by Surendra Singhi 05 Dec '04

05 Dec '04

Hi, I have a question about how to kill/stop/terminate the function execution while using slime and clisp? Thanks in advance. -- Surendra Singhi www.public.asu.edu/~sksinghi

3 6

[slime-devel] sldb keybinding feature request
by Dan Knapp 05 Dec '04

05 Dec '04

I haven't updated in a couple weeks, so perhaps this is already in CVS. When I am in sldb and accidentally enter a second debug level, and want to return to the first level, my first impulse is to hit "q". Of course, this blows away both levels and thus discards the debug information I was trying to use. Rather than curb my impulse, I would prefer that you make it do what I want. ^_^ You can use capital "Q" to mean "leave all levels of sldb". If you are worried about first-time users being confused ("I can't get out of the debugger!"), perhaps a warning would be appropriate. What do you all think? -- Dan Knapp

2 1

[slime-devel] Improved slime-global-variable-name-p
by Lynn Quam 05 Dec '04

05 Dec '04

I recommend the following change to SLIME-GLOBAL-VARIABLE-NAME-P so that package-qualified global variables are recognized. (defun slime-global-variable-name-p (name) "Is NAME a global variable? Globals are recognised purely by *this-naming-convention*." ;(string-match "^\\*.*\\*$" name) ;; LHQ Sat Nov 27 2004 -- allow optional <package-name>: or <package-name>:: (string-match "^\$.*::?\$?\\*.*\\*$" name) )

3 3

[slime-devel] serious xemacs/slime bug
by Surendra Singhi 30 Nov '04

30 Nov '04

Hi, I am using slime-1.0 and Xemacs 21.13. At times while running a lisp program through slime due to some error in the code the slime connection terminates. And then when I try to execute some command which if accidently depends upon slime then my xemacs hangs waiting for slime to respond, which on turn is waiting on clisp or someone. This causes the whole xemacs to hang, and I am not able to execute any command, though I am able to maximiaze/minimize, look at the menu bar etc. I feel there is some serious multi-threading issue which needs to be resolved(if it hasn't already been). Thanks. -- Surendra Singhi www.public.asu.edu/~sksinghi

4 5