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

[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 28 Sep '04

28 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

Re: [slime-devel] Emacs command for loading Slime and application
by Helmut Eller 28 Sep '04

28 Sep '04

Nicolas Neuss <Nicolas.Neuss(a)iwr.uni-heidelberg.de> writes: > 1. If Slime is not already running, the load command is not executed. > > 2. If Slime is already running, Femlisp is loaded, but the package is not > set. > > Can someone tell me how I can achieve my goal? Yes, this is bit more difficult because most of the commands work asynchronously. I changed slime-start-and-load a bit so that it should be usable for your needs. In general If you need commands of this sort, it's usually the easiest to write a small CL function for the job, so that Emacs can make a single RPC and doesn't need so much synchronization. > PS: Another problem is that executing (slime) apparently sets back some > variables, e.g. *READ-DEFAULT-FLOAT-FORMAT* which I have set to > DOUBLE-FLOAT when loading Femlisp. Why is that? Can't help you here without more details. Which Lisp are you using? Which communication style? Are threads involved? We don't set *READ-DEFAULT-FLOAT-FORMAT* explicit, but there's always the possibility for bug and that we used WITH-STANDARD-IO-SYNTAX in a wrong place. Helmut.

2 4

[slime-devel] Eval defun and compile defun failing on long functions
by Dan Pierson 28 Sep '04

28 Sep '04

Using a version of cmucl similar to 19a slime dies with the following in the *inferior lisp* buffer: ;; Connection to Emacs lost. ;; [Error in function LISP::ASSERT-ERROR: Short read: length=5467 pos=4093] Which looks rather like a packet lenth error of some sort -- 4093 seems suspicious to me. Does anyone have any ideas on how to look into this further? Dan Pierson

2 2

[slime-devel] (no subject)
by Pascal J.Bourguignon 28 Sep '04

28 Sep '04

In a Macintosh Programmer Workshop window: echo Hello Command-RETURN inserts: Hello in the window at the current position. In a Smalltalk Workspace window: 1 + 2 . A-d inserts 3 in the Workspace window at the current position. In an emacs lisp source buffer: (insert "\nHello\n") C-u C-x C-e inserts: Hello nil in the current buffer at the point. In a Common-Lisp source buffer with ilisp: (format t "~&Hello") C-z C-e inserts: Hello NIL in the current buffer at the point. In a Common-Lisp source buffer with slime: (format t "~&Hello") C-x C-e inserts nothing. Hides the result as soon as I type or move the mouse (like for example try to copy-and-paste it from the mini buffer, and I have to manipulate buffers, to reduce the size of my source, to hide it entirely to show the whole output that has been sent in some other buffer. Why so much hatred? I want both the output and the result of the function to be inserted at the point! How can that be done with slime? -- __Pascal Bourguignon__ http://www.informatimago.com/ Our enemies are innovative and resourceful, and so are we. They never stop thinking about new ways to harm our country and our people, and neither do we.

2 2

[slime-devel] Error: Attempting to change the lambda list of swank-compile-string
by John M. Adams 27 Sep '04

27 Sep '04

Dear Friends, Using fresh 1.0 cvs with ACL 7.0 beta I observe: ; Fast loading ; /home/jmadams/.slime/fasl/allegro-7.0.beta/swank-backend.fasl ; ... Error: Attempting to change the lambda list of #<STANDARD-GENERIC-FUNCTION SWANK-COMPILE-STRING> to (STRING &KEY BUFFER POSITION DIRECTORY) results in a confict with method #<STANDARD-METHOD SWANK-COMPILE-STRING (T)> Restart actions (select using :continue): 0: Remove this method 1: retry the load of /home/jmadams/.slime/fasl/allegro-7.0.beta/swank-backend.fasl 2: skip loading /home/jmadams/.slime/fasl/allegro-7.0.beta/swank-backend.fasl 3: retry the load of /home/jmadams/w/slime/swank-loader.lisp 4: skip loading /home/jmadams/w/slime/swank-loader.lisp 5: recompile /home/jmadams/w/slime/swank-loader.lisp 6: Return to Top Level (an "abort" restart). 7: Abort entirely from this (lisp) process. I see that others have reported similar problems, but I have seen no confirmed explanation. Has anyone actually got around this problem? I saw a suggestion that this might be caused by inadvertantly mixing different versions of swank.lisp and slime.el but I don't think that is the problem. I also saw that Helmut couldn't reproduce the problem, but I don't know what ACL version was being referred to. Thanks a lot,

2 1

[slime-devel] Re: SLIME docs
by Dan Pierson 27 Sep '04

27 Sep '04

Christian Lynbech wrote: > I wondered if the docs should mention usefull hacks to set up > functions to start slime with specialised lisp binaries/arguments (for > instance a special core image). I used to use something like these and rather miss them. The problem is that I find ,restart-inferior-lisp too useful to give up and it ignores all of this. Any suggestions for how to fix that? Dan Pierson

3 3

[slime-devel] Common Lisp Browser
by Rui Patrocínio 27 Sep '04

27 Sep '04

Hello, I've attached an extensible browser that I hope is useful and simple enough. It uses a lazy mechanism to expand the information required, so that it can be used to explore large systems. Currently it permits to explore class hierarchies and some xref information. I've a big hack that permits to see trace output in a tree-like fashion, but it's very ugly and implementation dependent and so it hasn't been included. A small interface in swank.lisp is needed, using the new API to MOP in the swank-backend: (defun class-direct-classes (class-name fn) (let ((class (find-class class-name nil))) (when class (mapcar #'(lambda (x) (symbol-name (class-name x))) (funcall fn class))))) (defslimefun mop (type symbol-name) "Return info about classes using mop. When type is: :subclasses - return the list of subclasses of class. :superclasses - return the list of superclasses of class." (let ((symbol (parse-symbol-or-lose symbol-name *buffer-package*))) (ecase type (:subclasses (class-direct-classes symbol #'swank-mop:class-direct-subclasses)) (:superclasses (class-direct-classes symbol #'swank-mop:class-direct-superclasses))))) Rui Patrocínio

2 1