slime-devel

slime-devel@common-lisp.net

4231 discussions

[slime-devel] SLIME and Lispworks?
by Alain.Picard＠memetrics.com 27 Nov '03

27 Nov '03

Dear SLIME developers (hi Luke!) Well, ILISP has been annoying me _SO_ much recently I figured it may finally be time to do something about it; then I stumbled on this project. I realize (from reading your sources so far) that you're focussing on CMUCL and SBCL; however, if the intent is to try to make the protocol sufficiently general/portable to other Lisps, I hereby volunteer my services as Lispworks user/tester/debugger (and even, initially) porter of whatever LW specific code needs to be written to get SLIME going on LW. I can't promise I have a lot of time to devote to this, so I'll be happy to pass the ball on to whoever wants to take this up next, but one is greater than zero, so I'm willing to give this a go, if the concensus of this list is that this is a) feasible b) a good idea So let me know your thoughts. (I won't be offended if you think such an effort is undesirable or premature, so feel free to speak your collective minds). yours, --Alain Picard

3 12

[slime-devel] ilisp-style symbol completion patch
by xach＠xach.com 27 Nov '03

27 Nov '03

Attached is a patch that, along with completer.el from ILISP, adds partial ILISP-style symbol completion to SLIME. Zach

2 2

[slime-devel] SLIME
by Luke Gorrie 27 Nov '03

27 Nov '03

G'day ILISP hackers, I should've written earlier to introduce our project called "SLIME" to you guys. It's similar to ILISP, the main differences are that we use a TCP socket to talk to Lisp and we generally try to imitate the Emacs Lisp programming interface. It started out a few months ago as a hack by Eric Marsden for highlighting CMUCL's compiler warnings in Emacs buffers, but other people started playing with it and now it's snowballed. The main page is on Cliki at http://www.cliki.net/SLIME if you want to know more. I'm not sure how all this relates to ILISP exactly, but I just wanted to shoot you a note to say hello and invite you to play around with it! Cheers, Luke

1 0

[slime-devel] SLIME and SBCL complaints about closed file descriptors
by Daniel Barlow 26 Nov '03

26 Nov '03

There is a long-standing bug in SBCL with sockets and finalisers that probably affects SLIME users more than anyone else. If you get errors about closed file descriptors while trying to do compilations, this is probably why. The fix is in SBCL CVS now (may be tomorrow by the time it gets into anoncvs) or you can patch an older SBCL by adding the following code to .sbclrc or somewhere suitable (in-package :sb-bsd-sockets) (defmethod socket-close ((socket socket)) (let ((fd (socket-file-descriptor socket))) (cond ((eql fd -1) ; already closed nil) ((slot-boundp socket 'stream) (close (slot-value socket 'stream)) ;; closes fd (setf (slot-value socket 'file-descriptor) -1) (slot-makunbound socket 'stream)) (t (sb-ext:cancel-finalization socket) (handler-case (if (= (sockint::close fd) -1) (socket-error "close")) (bad-file-descriptor-error (c) (declare (ignore c)) nil) (:no-error (c) (declare (ignore c)) nil)))))) -dan -- http://web.metacircles.com/ - CL custom development and SBCL support

1 0

[slime-devel] Users!
by Luke Gorrie 26 Nov '03

26 Nov '03

Avast mateys! I have come to the shocking realisation that we actually have USERS! Good heavens.. we haven't really prepared for this. I feel like the proverbial guy who forgot he was hosting a party and only had light beer when the guests arrived. What we need is a way for new users to find out how to use SLIME -- what some would call a manual. We need the information to be easy to update and get feedback on and for changes to be easy to follow. Sounds like a job for Cliki! So I've started a couple of new pages there: http://www.cliki.net/SLIME-HOWTO The mundane stuff - how to download and install. http://www.cliki.net/SLIME%20Features What features we have and how to use them. I have only made a start on the Features page. It would be great if newcomers to SLIME post little notes pointing out important information that's missing, and if seasoned users and hackers help them out and write a few words about their favourite features. What else can we do to help people use SLIME, beyond hacking? Cheers, Luke

5 8

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 26 Nov '03

26 Nov '03

Index: slime/ChangeLog diff -u slime/ChangeLog:1.111 slime/ChangeLog:1.113 --- slime/ChangeLog:1.111 Mon Nov 24 19:22:11 2003 +++ slime/ChangeLog Tue Nov 25 16:28:23 2003 @@ -1,3 +1,14 @@ +2003-11-25 Luke Gorrie <luke(a)bluetail.com> + + * slime.el (slime-make-typeout-frame): New command to create a + frame where commands can print messages that would otherwise go to + the echo area. + (slime-background-message): Function for printing "background" + messages. Uses the "typeout-frame" if it exists. + (slime-arglist): Print arglist with `slime-background-message'. + (slime-message): Use typeout frame if it exists, but only for + multi-line messages. + 2003-11-25 Daniel Barlow <dan(a)telent.net> * swank-sbcl.lisp: delete big chunk of leftover commented-out

1 0

[slime-devel] And now for something completely different..
by Luke Gorrie 25 Nov '03

25 Nov '03

I'm really enjoying this (the OSX people had made me jealous): http://www.bluetail.com/~luke/misc/emacs/gnus-truetype-x11.png -Luke

2 2

[slime-devel] Asynchronous debugging
by Daniel Barlow 25 Nov '03

25 Nov '03

More on yesterday's experiments. The attached patch (1) adds :debug as a valid state transition from the idle state (2) adds SLIME-DEBUGGER-FUNCTION. This expects to be run in an environment in which the slime streams are available (e.g. from *slime-repl* or, I think, with C-c :) and returns a function that can be used for *debugger-hook* or *invoke-debugger-hook* Note that (setf sb-debug::*invoke-debugger-hook* (slime-debugger-function)) doesn't actually work from *slime-repl* because the hook has already been bound so you're not setting the global value. Answers on a postcard. (3) Changes eval-string to use *invoke-debugger-hook* instead of ordinary *debugger-hook* - because it's safe for BREAK, and also so it doesn't conflict with my existing (notionally portable) *debugger-hook* use in Araneida If I culd figure out an appropriate place to put it, I'd want to make this a (with-debugging-hooked ...) macro, but I think that needs build order frobbing The combined effect is that I can now use sldb when Araneida handlers cause errors. Setup recipe: CL-USER> (asdf:operate 'asdf:load-op 'araneida) .... CL-USER> (load "/home/dan/src/telent/araneida/doc/example") T CL-USER> (araneida:start-listening my-araneida-example::*listener*) #<SB-IMPL::HANDLER INPUT on descriptor 5: #<FUNCTION "CLOSURE" {96F8645}>> CL-USER> (setf araneida::*break-on-handler-errors* t) T CL-USER> (defvar *foo* (swank::slime-debugger-function)) #<FUNCTION "CLOSURE" {96F9815}> ;;; meanwhile in *inferior-lisp* * (setf sb-debug::*invoke-debugger-hook* cl-user::*foo*) I haven't applied this; it's more intended for discussion at present (particularly point (2)). Comments? -dan -- http://web.metacircles.com/cirCLe_CD - Free Software Lisp/Linux distro

3 7

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 25 Nov '03

25 Nov '03

Index: slime/ChangeLog diff -u slime/ChangeLog:1.109 slime/ChangeLog:1.111 --- slime/ChangeLog:1.109 Sun Nov 23 22:24:36 2003 +++ slime/ChangeLog Mon Nov 24 19:22:11 2003 @@ -1,4 +1,17 @@ +2003-11-25 Daniel Barlow <dan(a)telent.net> + + * swank-sbcl.lisp: delete big chunk of leftover commented-out + code + + * slime.el: arglist command to use slime-read-symbol-name, + not slime-read-symbol + + * README: Minor updates for currency + 2003-11-24 Luke Gorrie <luke(a)bluetail.com> + + * swank-backend.lisp (compiler-condition): Removed use of + :documentation slot option. That is not portable (to CMUCL 18e). * swank.lisp (eval-string-in-frame): Fixed symbol-visibility problem (thanks Lawrence Mitchell).

1 0

[slime-devel] Slime and sbcl, minor problems.
by lawrence mitchell 24 Nov '03

24 Nov '03

So I'm trying to get slime and sbcl working together happily. Versions: SBCL 0.8.5.50 (CVS as of 2003/11/23) Slime (CVS as of 2003/11/23) In order to get slime to work properly, I needed to make two minor modifications to swank-sbcl.lisp and swank.lisp. The change to swank-sbcl.lisp was to allow SLIME-EDIT-FDEFINITION to work properly. The pathname returned by SWANK:FUNCTION-SOURCE-LOCATION hadn't been resolved via sbcl's LOGICAL-PATHNAME-TRANSLATIONS. Hence, Emacs was sending me to buffers like "SYS:SRC;CODE;DEFMACRO.LISP", rather than "/opt/cvs-trees/sbcl/src/code/defmacro.lisp". Not knowing whether this is even vaguely correct, I added a TRUENAME call as below: Index: swank-sbcl.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/swank-sbcl.lisp,v retrieving revision 1.26 diff -u -r1.26 swank-sbcl.lisp --- swank-sbcl.lisp 23 Nov 2003 14:16:42 -0000 1.26 +++ swank-sbcl.lisp 23 Nov 2003 17:40:11 -0000 @@ -324,7 +324,7 @@ (pathname (sb-introspect:definition-source-pathname def)) (path (sb-introspect:definition-source-form-path def))) (list :sbcl - :filename (and pathname (namestring pathname)) + :filename (and pathname (namestring (truename pathname))) :position (sb-introspect:definition-source-character-offset def) :path path ;; source-paths depend on the file having been compiled with The second problem was rather more severe, since swank-sbcl.lisp doesn't define SWANK:EVAL-IN-FRAME, there was a compilation reader error on compiling swank.lisp, specifically: | compilation aborted because of input error: | READ failure in COMPILE-FILE: | READER-ERROR at 8809 (line 270, column 41) on | #<FILE-STREAM for "file \"/opt/cvs-trees/slime/swank.lisp\"" {9AFF329}>: | The symbol "EVAL-IN-FRAME" is not external in the SWANK package. Further, once the slime startup process was almost finished, it entered an infinite loop, which, when interrupted, printed the following error message in *inferior-lisp* buffer: | ;; Connection to Emacs lost. | ;; [READER-ERROR at 18 (line 1, column 18) on #<SB-IMPL::STRING-INPUT-STREAM | {9D591E9}>: | Symbol "EVAL-STRING" not found in the SWANK package.] The Elisp debugger output on C-g was: | Debugger entered--Lisp error: (quit) | (eq (slime-state-name (slime-current-state)) | (quote slime-evaluating-state)) | slime-busy-p() | (while (slime-busy-p) (accept-process-output)) | (let ((debug-on-quit t) (inhibit-quit nil)) | (while (slime-busy-p) (accept-process-output))) | slime-do-eval((swank:getpid) nil (:catch-tag slime-result-76376)) I fixed this by making this modification to swank.lisp: Index: swank.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/swank.lisp,v retrieving revision 1.64 diff -u -r1.64 swank.lisp --- swank.lisp 23 Nov 2003 14:16:42 -0000 1.64 +++ swank.lisp 23 Nov 2003 17:46:07 -0000 @@ -267,7 +267,7 @@ (continue *swank-debugger-condition*)) (defslimefun eval-string-in-frame (string index) - (to-string (swank-backend:eval-in-frame (from-string string) index))) + (to-string (swank-backend::eval-in-frame (from-string string) index))) ;;;; Evaluation Whilst this is probably not at all correct, "it works for me". -- lawrence mitchell <wence(a)gmx.li>

3 5

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel