slime-devel

slime-devel@common-lisp.net

4231 discussions

[slime-devel] #+#. bug report (with fix, maybe)
by Luis Oliveira 27 Jan '08

27 Jan '08

Hello, While trying to compile some code that contained the #+#. idiom I came across a bug in SLIME. Here's a minimal test case: (defun foo () #+#.'(:and) (/ 1 0)) And some variations: (defun foo () #+#.'(:and) t (/ 1 0)) (defun foo () (let (unused) #+#.'(:and) t)) Trying to compile these examples through, e.g., slime-compile-file or slime-compile-defun results in a cryptic error: unknown operator in feature expression: (#:|#.1|). [Condition of type SIMPLE-ERROR] What these three examples have in common is that a compiler note is generated and the offending form contains #+#. which makes SWANK-BACKEND::LOCATE-COMPILER-NOTE choke. What happens is that READ-AND-RECORD-SOURCE-MAP overrides #. and makes it return a gensym, #:|#.1| in this particular example, which is then passed to #+ and causes the error above. SUPPRESS-SHARP-DOT sets things up so that #. returns a gensym instead of NIL in order to "avoid multiple entries for nil at toplevel in the source-map", according to the ChangeLog. Even if we ignore that problem, having #. return NIL in this case, while it would dodge the error, it wouldn't find or properly annotate the offending (/ 1 0) form since #+cl:nil usually suppresses forms. The attached patch gets rid of SUPPRESS-SHARP-DOT. That not only fixes my original problem but also makes the following example work better than it before, since the (/ 1 0) form is now annotated: #.'(defun foo () (/ 1 0)) I believe that was the case the ChangeLog entry I quoted was referring to. However, I have the feeling that there might be some good reason why #. was suppressed in the first place. Any ideas? (BTW, it took me a while to figure out this bug was coming from within SLIME itself, and it might have taken even longer if someone hadn't noticed that compiling the software in question without SLIME worked without problem. Perhaps it would be helpful to somehow report internal errors as such?) -- Luís Oliveira http://student.dei.uc.pt/~lmoliv/

2 1

[slime-devel] slime-load-system
by Joris Bleys 23 Jan '08

23 Jan '08

Hi, I seem to be unable to use the 'M-x slime-load-system' function which seems to be also missing in my slime.el file. Is my system wrongly configured or is this function abandoned? My current set-up: - slime 2007-12-14 (downloaded from CVS repository) - carbon emacs (winter 2008 edition, from http://homepage.mac.com/zenitani/emacs-e.html) - sbcl 1.0.13 Many thanks in advance, Joris

2 2

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 21 Jan '08

21 Jan '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1271 slime/ChangeLog:1.1272 --- slime/ChangeLog:1.1271 Sun Jan 20 11:18:59 2008 +++ slime/ChangeLog Mon Jan 21 06:51:07 2008 @@ -1,3 +1,11 @@ +2008-01-21 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (sldb-mode): Don't throw to toplevel in the + kill-buffer-hook, since the buffer can be killed for other reasons + too. + (test break): Test BREAK and CONTINUE in a loop. + (slime-wait-condition): Display the current time. + 2008-01-20 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> New hooks that allow the slime-presentations contrib to hook @@ -94,7 +102,7 @@ * swank.lisp (read-softly-from-string): Now actually returns all three values as explained in its docstring. - + 2007-12-14 Tobias C. Rittweiler <tcr(a)freebits.de> * slime.el (slime-insert-xref-location): New function. Tries to

1 0

[slime-devel] Selecting the CONTINUE restart
by Ralf Mattes 21 Jan '08

21 Jan '08

I'm trying to select a CONTINUE restart that offers to modify a place from within the slime debugger but, alas, this doesn't work. Even so I get prompted for a new value (in the REPL, not in the debugger) the evaluation gets aborted. Here's a (primitive) test case: CL> (defparameter x 42) X CL> (assert nil (X) "Something fishy") Something fishy [Condition of type SIMPLE-ERROR] Restarts: 0: [CONTINUE] Retry assertion with new value for X. 1: [ABORT] Return to SLIME's top level. 2: [ABORT] Exit debugger, returning to top level. Backtrace: 0: (SB-KERNEL:ASSERT-ERROR NIL (X) "Something fishy") 1: (NIL) (user enters '0' or 'C' here ...) The old value of X is 42. Do you want to supply a new value? (y or n) ; Evaluation aborted. CL> The same test works from the lisp REPL. My system: CL> (lisp-implementation-type) "SBCL" CL> (lisp-implementation-version) "1.0.10.debian" Slime is a current CVS checkout. TIA Ralf Mattes

2 2

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 20 Jan '08

20 Jan '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1269 slime/ChangeLog:1.1271 --- slime/ChangeLog:1.1269 Sat Jan 19 10:09:31 2008 +++ slime/ChangeLog Sun Jan 20 11:18:59 2008 @@ -1,3 +1,22 @@ +2008-01-20 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> + + New hooks that allow the slime-presentations contrib to hook + into the debugger and inspector. + + * slime.el (sldb-insert-frame-variable-value-function): New + variable. + (sldb-insert-frame-variable-value): New function, default value + for sldb-insert-frame-variable-value-function. + (sldb-insert-locals): Use it here. + + * slime.el (slime-inspector-insert-ispec-function): New variable. + (slime-open-inspector): Use it here. + +2008-01-20 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> + + * doc/slime.texi (Presentations): Improve documentation of + presentations. + 2008-01-19 Geo Carncross <geocar(a)gmail.com> * swank-ecl.lisp (inspect-for-emacs): Make ECL inspection better; Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.79 slime/contrib/ChangeLog:1.80 --- slime/contrib/ChangeLog:1.79 Sat Jan 19 09:08:27 2008 +++ slime/contrib/ChangeLog Sun Jan 20 11:18:49 2008 @@ -1,3 +1,16 @@ +2008-01-20 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> + + Hook presentations into debugger and inspector, restoring + features that were removed on 2007-08-27. + + * slime-presentations.el (slime-presentation-add-easy-menu): + Install presentation menu also in the debugger and inspector. + (slime-presentation-inspector-insert-ispec): New. + (slime-presentation-sldb-insert-frame-variable-value): New. + (slime-presentations-init): Install these functions as + slime-inspector-insert-ispec-function and + sldb-insert-frame-variable-value-function. + 2008-01-19 Helmut Eller <heller(a)common-lisp.net> * swank-goo.goo: New file.

1 0

[slime-devel] [BUG] Weird interplay between SLDB, condition system, and READ
by Tobias C. Rittweiler 20 Jan '08

20 Jan '08

Hi all, The following works in a raw SBCL session, but not when used with Slime: (defun call-with-retry-restart (msg thunk) (restart-bind ((retry (lambda () (throw 'retry nil)) :report-function (lambda (stream) (write msg :stream stream)))) (catch 'ok (loop do (catch 'retry (format t "CATCH 'RETRY~%") (throw 'ok (funcall thunk))) (format t "LOOP~%"))))) (defmacro with-retry-restart ((&key (msg "Retry.")) &body body) (check-type msg string) `(call-with-retry-restart ,msg #'(lambda () ,@body))) (with-retry-restart () (format t "BODY~%") (unless (equal (read) "OUTTA") (error "Lost in a maze!"))) After having invoked the retry restart, the new computation is aborted by the call to READ. I tried to get at what's causing this, but ran out of time. Perhaps you're luckier. Thanks in advance. -T.

3 2

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 19 Jan '08

19 Jan '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1268 slime/ChangeLog:1.1269 --- slime/ChangeLog:1.1268 Thu Jan 17 00:53:44 2008 +++ slime/ChangeLog Sat Jan 19 10:09:31 2008 @@ -1,3 +1,8 @@ +2008-01-19 Geo Carncross <geocar(a)gmail.com> + + * swank-ecl.lisp (inspect-for-emacs): Make ECL inspection better; + should be able to handle all builtin types and CLOS objects now. + 2008-01-17 Nikodemus Siivola <nikodemus(a)random-state.net> * swank-sbcl.lisp (sbcl-source-file-p): When a buffer is not Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.78 slime/contrib/ChangeLog:1.79 --- slime/contrib/ChangeLog:1.78 Fri Jan 11 08:06:45 2008 +++ slime/contrib/ChangeLog Sat Jan 19 09:08:27 2008 @@ -1,3 +1,8 @@ +2008-01-19 Helmut Eller <heller(a)common-lisp.net> + + * swank-goo.goo: New file. + * swank-kawa.scm: New file. + 2008-01-11 Stelian Ionescu <sionescu(a)common-lisp.net> * slime-presentations.el

1 0

[slime-devel] Mailing List Question
by Zach Calvert 19 Jan '08

19 Jan '08

Is this mailing list for general questions using Slime or for Slime development only? If Slime development only, is there a general usage/newbie question mailing list? Thank you, Zach Calvert

3 4

[slime-devel] What's new in slime?
by Sunil Mishra 18 Jan '08

18 Jan '08

This has got to be a FAQ, only I don't know if there is a SLIME FAQ... I have been waiting for a new official release of slime for some time. But there hasn't been one since 2006. I'm not sure where I should look to find out what I can do with the current CVS of SLIME either. Can anyone offer pointers on where I should look to learn what's changed since 2006? Thanks, Sunil

2 2

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 17 Jan '08

17 Jan '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1267 slime/ChangeLog:1.1268 --- slime/ChangeLog:1.1267 Mon Jan 14 07:08:52 2008 +++ slime/ChangeLog Thu Jan 17 00:53:44 2008 @@ -1,3 +1,9 @@ +2008-01-17 Nikodemus Siivola <nikodemus(a)random-state.net> + + * swank-sbcl.lisp (sbcl-source-file-p): When a buffer is not + associated with any file, M-. for names defined there ends up + calling SBCL-SOURCE-FILE-P with NIL -- guard against that. + 2008-01-14 Tobias C. Rittweiler <tcr(a)freebits.de> * slime.el (sldb-mode): Add `sldb-quit' to `kill-buffer-hook' to

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel