slime-devel June 2006

slime-devel@common-lisp.net

33 participants
36 discussions

Re: [slime-devel] Unable to get SLIME working with sbcl-0.9.13
by rif 12 Jun '06

12 Jun '06

Ah, maybe I spoke too soon. Apparently, I need to set swank:*communication-style* to something other than :spawn. Is it known that :spawn doesn't work with sbcl? I somehow thought I'd been using :spawn with sbcl on my other (home) machine, but maybe I was confused. rif

4 3

[slime-devel] Unable to get SLIME working with sbcl-0.9.13
by rif 12 Jun '06

12 Jun '06

Does slime work with the newest SBCL? I've tried both the CVS snapshot and the 2.0 release. In both cases, it seems to build a bunch of stuff, then gives me a prompt and instantaneously crashes ("Lisp connection closed unexpectedly: exited abnormally with code 256"). The last WARNING printed in *inferior-lisp* (ignoring style warnings) is WARNING: These Swank interfaces are unimplemented: (ACTIVATE-STEPPING CALLS-WHO DISASSEMBLE-FRAME INSPECT-FOR-EMACS SLDB-BREAK-AT-START SLDB-BREAK-ON-RETURN WHO-BINDS WHO-CALLS WHO-MACROEXPANDS WHO-REFERENCES WHO-SETS WHO-SPECIALIZES) What am I doing wrong? Do I need to back off to an earlier SBCL? rif

1 0

[slime-devel] seting default directory
by Nikola Skoric 12 Jun '06

12 Jun '06

Hi there, I can't find out how I can set default directory in which slime should run. I tried to add (set-default-directory "foobar") to site-init.lisp, but things don't go that way, it seems to me... -- sig

4 3

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 12 Jun '06

12 Jun '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.905 slime/ChangeLog:1.906 --- slime/ChangeLog:1.905 Fri Jun 9 23:27:03 2006 +++ slime/ChangeLog Sun Jun 11 07:02:08 2006 @@ -1,4 +1,9 @@ +2006-06-11 Douglas Crosher <dcrosher(a)common-lisp.net> + + * swank-scl (ext:stream-write-chars): update for SCL 1.3. + 2006-06-09 Alan Ruttenberg <alanr-l(a)mumble.net> + * swank-abcl: Update to cvs version of abcl and warnings errors when compiling in a buffer will now be properly caught by slime vs current behavior of always saying 0 errors 0 warnings and printing

1 0

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 10 Jun '06

10 Jun '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.904 slime/ChangeLog:1.905 --- slime/ChangeLog:1.904 Wed May 31 15:27:31 2006 +++ slime/ChangeLog Fri Jun 9 23:27:03 2006 @@ -1,3 +1,9 @@ +2006-06-09 Alan Ruttenberg <alanr-l(a)mumble.net> + * swank-abcl: Update to cvs version of abcl and warnings errors + when compiling in a buffer will now be properly caught by slime vs + current behavior of always saying 0 errors 0 warnings and printing + them in the repl instead + 2006-05-31 Nathan Bird <nathan(a)acceleration.net> * swank.lisp (*sldb-quit-restart*): New variable.

1 0

[slime-devel] How to determine the top caller in Slime's REPL
by Philippe-André Lorin 09 Jun '06

09 Jun '06

Hello everybody. I'm a Slime newbie, trying to develop an application that is intended to be run in Emacs + Slime to allow for interactive modifications. I posted this to comp.lang.lisp, but got few replies; it is probably more appropriate here. In Slime, I need to be able to determine dynamically whether the "top caller" of the currently executing code is some specifically marked expression, or just one of all the other expressions typed at the REPL which might be running in parallel. An example should make the idea clearer. (defun f () ; This function is just here to show that the (in-marked-expression)) ; test is not necessarily lexically enclosed ; in the marked expression. (mark-and-eval (do () (nil) ; Just an infinite loop, to make sure the ; expression will be running forever in parallel. (assert (f)))) ; Here, IN-MARKED-EXPRESSION must always return T. (f) ; Note that the preceding (DO ...) is still running. => NIL ; Here, IN-MARKED-EXPRESSION must always return NIL. I can write the marked expression with complete freedom (for instance, I can add wrappers around it or preprocess it), but all the other expressions typed after it at the REPL are not under my control. Among the ideas I've tested, the following one sounded the most promising, but it doesn't work. I don't understand why. (defun in-marked-expression () (not (null (find-restart 'restart-in-restart-case)))) ; Are we in the ; restart-case? (defun f () (in-marked-expression)) (restart-case (do () (nil) (assert (f))) (restart-in-restart-case () nil)) (f) => T ; :( I also tried using a special variable or processes, with no luck. Any ideas? PS: I'm using CMUL on Ubuntu.

1 0

[slime-devel] Slime/CMU hangs on GC
by Florian Ebeling 05 Jun '06

05 Jun '06

My emacs in slime mode hangs quite oft imidiatly after announcing a GC run, usually from a Slime mode buffer, not from REPL. I use CMUCL and Slime from CVS. Is this a known behaviour? Florian -- Florian Ebeling florian.ebeling(a)gmail.com

4 3

[slime-devel] slime-apropos problem
by jcb 05 Jun '06

05 Jun '06

slime-apropos is behaving strangely on my system: PowerBook G4 Mac OS X 10.4.6 sbcl 0.9.13 Aquamacs 0.9.9c Here is what happens: 1. Start SLIME M-x slime 2. Try slime-apropos on "*package*" C-c C-d a SLIME Apropos: *package* 3. Check % CPU activity in Activity Monitor.app: the sbcl process hovers constantly at around 85%. It makes the fans come on :-). slime-apropos seems to work ok with e.g. "defun". Try it with "*default-pathname-defaults*", and it'll peg the sbcl process. This behavior happens with both SLIME from CVS and SLIME 2.0. Clues? Known issue? Anymore info needed...? Thanks..

3 2

[slime-devel] Better .asd
by Greg Pfeil 04 Jun '06

04 Jun '06

After being confused as to why (asdf:oos 'asdf:load-op :swank) wasn't working, I decided to look at the source to figure it out. The problem was that I was using ASDF-Binary-Locations to store my fasls elsewhere on the disk, and once swank-loader.fasl was put in the alternate location, it couldn't find any of the other swank .lisp files. I created a new swank.asd that contains (I think) the full functionality of swank-loader.lisp. This allows the fasls to be relocated. I know, this means that changes have to happen in two places. I think there's a solution to this, too. Rather than have the .asd call swank-loader, reverse it. Write a new swank-loader that just loads the .asd (untested): (defvar *source-directory* (make-pathname :name nil :type nil :defaults (or *load-pathname* *default-pathname- defaults*)) "The directory where to look for the source.") (handler-case (require :asdf) (condition () (load (make-pathname "asdf" :defaults *source-directory*)) (pushnew *source-directory* asdf:*central-registry* :test #'equal))) (asdf:oos 'asdf:load-op :swank) This tries to use an ASDF outside of the swank directory first, but falls back to an included one if need be. Then it loads the system. This means that for the time being, slim.e-el (and anyone setting the slime-backend custom variable) doesn't have to change anything. I know, it adds a dependency, but asdf is pretty ubiquitous anymore, and the inclusion of a fallback version in the source should catch a lot of the other cases. Cons: - requires ASDF Pros: - can eliminate a bunch of code used to manage file locations - gain flexibility of ASDF and its extensions (like ASDF-Binary- Locations) It also seems like SWANK maybe should be made into its own ASDF- Installable package, with SLIME having only the emacs code and SWINE having the Climacs code. Does anyone think any of this might be a good idea?

2 1

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 01 Jun '06

01 Jun '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.903 slime/ChangeLog:1.904 --- slime/ChangeLog:1.903 Mon May 29 19:41:00 2006 +++ slime/ChangeLog Wed May 31 15:27:31 2006 @@ -1,3 +1,9 @@ +2006-05-31 Nathan Bird <nathan(a)acceleration.net> + + * swank.lisp (*sldb-quit-restart*): New variable. + (throw-to-toplevel): Use the restart named by *sldb-quit-restart* + as opposed to hard coding abort-request. + 2006-05-30 Tobias Rittweiler <tcr(a)freebits.de> * slime.el (slime-get-temp-buffer-create): New keyword REUSEP

1 0

[slime-devel] Duplicate definitions in slime-edit-definition
by Chris Dean 01 Jun '06

01 Jun '06

I'm not sure if this happens in other Lisps, but in LispWorks I start to get duplicate definitions listed when I used SLIME-EDIT-DEFINITION to jump to a function. These are all the "same" function definition, just with a slightly different line numbers as I make changes to whatever .lisp file I'm editing and recompile the function. (This sure is tricky to explain!) I made a change to slime-edit-definition to remove the duplicates. Patch below. If this only happens in LispWorks I can modify swank-lispworks.lisp instead. Cheers, Chris Dean Index: slime.el =================================================================== RCS file: /project/slime/cvsroot/slime/slime.el,v retrieving revision 1.625 diff -u -w -r1.625 slime.el --- slime.el 29 May 2006 23:39:47 -0000 1.625 +++ slime.el 1 Jun 2006 02:08:02 -0000 @@ -6327,7 +6327,12 @@ (if slime-edit-definition-fallback-function (funcall slime-edit-definition-fallback-function name) (error "No known definition for: %s" name)) - (slime-goto-definition name definitions where)))) + (slime-goto-definition name + (remove-duplicates definitions + :key #'car + :test #'string= + :from-end t) + where)))) (defun slime-goto-definition (name definitions &optional where) (slime-push-definition-stack) Index: ChangeLog =================================================================== RCS file: /project/slime/cvsroot/slime/ChangeLog,v retrieving revision 1.904 diff -u -w -r1.904 ChangeLog --- ChangeLog 31 May 2006 19:27:31 -0000 1.904 +++ ChangeLog 1 Jun 2006 02:08:10 -0000 @@ -1,3 +1,8 @@ +2006-05-31 Chris Dean <ctdean(a)sokitomi.com> + + * slime.el (slime-edit-definition): Remove duplicate functions + names. + 2006-05-31 Nathan Bird <nathan(a)acceleration.net> * swank.lisp (*sldb-quit-restart*): New variable.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel June 2006