slime-devel

slime-devel@common-lisp.net

4231 discussions

[slime-devel] Errors with latest SLIME on SBCL
by Yarek Kowalik 06 Jun '08

06 Jun '08

I'm running into similar problems as this one with latest SLIME checked out from cvs, the only difference is the version of SBCL - 1.0.12: http://paste.lisp.org/display/61629 Any idea why I'm getting this? Any way to fix this? Thanks, Yarek

2 1

[slime-devel] Feature request: #+foo foo #-foo not-foo indentation
by Nikodemus Siivola 06 Jun '08

06 Jun '08

Currently, Slime indents like so: (defun foo (x) (typecase x (#+foo foo #-foo fake-foo :foo) (t :not-foo))) whereas it should be like so: (defun foo (x) (typecase x (#+foo foo #-foo fake-foo :foo) (t :not-foo))) Is there a way to coax Slime/Emacs to do the right thing here? Cheers, -- Nikodemus

2 1

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

02 Jun '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1356 slime/ChangeLog:1.1357 --- slime/ChangeLog:1.1356 Mon May 19 09:12:52 2008 +++ slime/ChangeLog Mon Jun 2 14:11:15 2008 @@ -1,3 +1,12 @@ +2008-06-02 Raymond Toy <toy.raymond(a)gmail.com> + + Unicode support for CMUCL. + + * swank-cmucl.lisp (accept-connection, make-socket-io-stream): + Handle external-format argument. + (find-external-format): Implemented. + (*external-format-to-coding-system*): New variable. + 2008-05-19 Helmut Eller <heller(a)common-lisp.net> * swank-sbcl.lisp: Don't require asdf.

1 0

[slime-devel] Re: function/symbol-function and thread binding bug?
by Rudi Schlatte 31 May '08

31 May '08

"Tobias C. Rittweiler" <tcr(a)freebits.de> writes: > szergling <senatorzergling(a)gmail.com> writes: > >> Hi folks, >> >> Perhaps I've confused myself a bit here, but there seem to be >> something wrong with either Slime (most likely), SBCL threads, or my >> understanding of the difference between (funcall 'print-something) and >> (funcall #'print-something). >> >> Could someone confirm the following behaviour? > > This is not a Slime issue; the analysis seems correct, though. You > shouldn't rely on this behaviour programmatically. HTH. > I say it's a misunderstanding of the difference between the two funcall examples. You can rely on (let ((that-which-i-want-to-call 'print-something)) (funcall that-which-i-want-to-call)) and (let ((that-which-i-want-to-call #'print-something)) (funcall that-which-i-want-to-call)) to have different semantics. This is not a bug. funcall takes a function designator, which can be a symbol or a function. If funcall is called with 'print-something, it picks up the function that that is currently residing in print-something's function cell. But a redefinition of print-something (which is just storing a new value in that symbol's function cell) doesn't magically hunt down and overwrite every function object (now not bound to any symbol's function attribute) that happened to have been stored in print-something's function cell at some point in the past. So, in the second example the same function will be called, no matter in what way print-something is manhandled in another thread. Cheers, Rudi

1 0

[slime-devel] function/symbol-function and thread binding bug?
by szergling 31 May '08

31 May '08

Hi folks, Perhaps I've confused myself a bit here, but there seem to be something wrong with either Slime (most likely), SBCL threads, or my understanding of the difference bet

1 0

[slime-devel] How to specify optimize options to C-c C-c
by Mirko Vukovic 29 May '08

29 May '08

Hello, When I develop new code (ok, I admit it, this is the first time I am developing code in lisp&slime), I put this at the beginning of the file: (declaim (optimize (safety 3)) (optimize (debug 3)) (optimize (speed 0))) This helps me in debugging the code. However, if I compile defun's with C-c C-c, it does not seem to use that rule. How can I force it to? Thank you, Mirko

3 2

[slime-devel] slime command for stepping a defun?
by Mirko Vukovic 28 May '08

28 May '08

Hello, Is there a slime command to execute (step (funct)) when the cursor is in funct? Thank you, Mirko

1 0

[slime-devel] Re: [Sbcl-devel] Trouble starting up SBCL
by Nikodemus Siivola 20 May '08

20 May '08

On Tue, May 20, 2008 at 4:03 AM, Olivier Drolet <trimtab(a)mac.com> wrote: > Greetings, > > I typed M-x slime in Aquamacs (1.3CVS) to start up SBCL (1.0.16) under > Mac OS X 10.5.2 (PPC iMac) and the thing hangs. I get this message: > > "error in process filter: Symbol's function definition is void: > defpackage" > > Any suggestions? Is this the right forum? slime-devel(a)common-lisp.net is probably better, since this sounds like an Emacs / Slime problem, so I added that to CC. (Please drop sbcl-devel from future replies.) What do you have in *slime-events* buffer? Cheers, -- Nikodemus

1 0

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

19 May '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1354 slime/ChangeLog:1.1356 --- slime/ChangeLog:1.1354 Sat May 17 07:03:19 2008 +++ slime/ChangeLog Mon May 19 09:12:52 2008 @@ -1,3 +1,16 @@ +2008-05-19 Helmut Eller <heller(a)common-lisp.net> + + * swank-sbcl.lisp: Don't require asdf. + +2008-05-19 Helmut Eller <heller(a)common-lisp.net> + + * swank-sbcl.lisp (swank-compile-string): Add reader-conditionals + for sb-ext::restrict-compiler-policy. + +2008-05-19 Geo Carncross <geocar(a)gmail.com> + + * contrib/swank-asdf.lisp: Require asdf. + 2008-05-17 Helmut Eller <heller(a)common-lisp.net> * slime.el (slime-prin1-to-string): Bind print-length and

1 0

Re: [slime-devel] leopard + sbcl + sb-thread
by Nikodemus Siivola 19 May '08

19 May '08

On Mon, May 19, 2008 at 4:58 AM, Aaron Feng <aaron.feng(a)gmail.com> wrote: > Hi Nikodemus, > >> This doesn't make sense to me. As far I've understood, the backtrace >> occurred in *inferior-lisp*, and there should be no "more" there after >> typing the "ba" at the debugger prompt. > > When I load up emacs this is *exactly* what I see: > > The value 68089408 is not of type SIMPLE-STRING. > [Condition of type TYPE-ERROR] > > Restarts: > 0: [ABORT] Return to SLIME's top level. > 1: [TERMINATE-THREAD] Terminate this thread (#<THREAD "worker" {14132649}>) > > Backtrace: > 0: (SB-KERNEL:%SXHASH-SIMPLE-STRING #<unavailable argument>) > 1: ((FLET SB-C::LOOKUP) (#<SB-C::VOLATILE-INFO-ENV "Working"> > #<SB-C::COMPACT-INFO-ENV #1="Auxiliary"> #<SB-C::COMPACT-INFO-ENV #1#>)) > 2: (MACRO-FUNCTION #<error printing object>) > --more-- I kind of wish you had posted this in the first place. :) Because your first message didn't have the [Condition of TYPE-ERROR] I assume that the debugger was the SBCL debugger inside *inferior-lisp*, not the Slime debugger inside an SLDB buffer -- and they work quite differently. At any rate, hitting neither ba not b will get you the backtrace we desire here. Here just clicking on the --more-- is indeed the right thing to do -- and if another --more-- appears further down clicking on it again till you have the full backtrace. ...but you don't need to do that now, since *slime-events* had everything I wanted to know. Just for future reference. In *slime-events* you have: ("The value 68089408 is not of type SIMPLE-STRING." " [Condition of type TYPE-ERROR]" nil) (("ABORT" "Return to SLIME's top level.") ("TERMINATE-THREAD" "Terminate this thread (#<THREAD \"worker\" {1411A649}>)")) ((0 "(SB-KERNEL:%SXHASH-SIMPLE-STRING #<unavailable argument>)") (1 "((FLET SB-C::LOOKUP) (#<SB-C::VOLATILE-INFO-ENV \"Working\"> #<SB-C::COMPACT-INFO-ENV #1=\"Auxiliary\"> #<SB-C::COMPACT-INFO-ENV #1#>))") (2 "(MACRO-FUNCTION #<error printing object>)") (3 "(SWANK::SYMBOL-INDENTATION #<error printing object>)") (4 "((FLET SWANK::CONSIDER) #<error printing object>)") (5 "((FLET SB-IMPL::ITERATE-OVER-HASH-TABLE) #<SB-IMPL::PACKAGE-HASHTABLE :SIZE 95 :FREE 36 :DELETED 0>)") (6 "(SWANK::UPDATE-INDENTATION/DELTA-FOR-EMACS #<HASH-TABLE :TEST EQ :COUNT 124 {14004AC1}> (#<PACKAGE \"SWANK-IO-PACKAGE\"> #<PACKAGE \"SWANK\"> #<PACKAGE \"SWANK-MOP\"> #<PACKAGE \"SWANK-BACKEND\"> #<PACKAGE \"SWANK-LOADER\"> #<PACKAGE \"WEBLOCKS-ASD\"> ...))") (7 "(SWANK::PERFORM-INDENTATION-UPDATE #<SWANK::CONNECTION {14004B11}> (#<PACKAGE \"SWANK-IO-PACKAGE\"> #<PACKAGE \"SWANK\"> #<PACKAGE \"SWANK-MOP\"> #<PACKAGE \"SWANK-BACKEND\"> #<PACKAGE \"SWANK-LOADER\"> #<PACKAGE \"WEBLOCKS-ASD\"> ...))") (8 "(SWANK::RUN-HOOK (SWANK::SYNC-INDENTATION-TO-EMACS SWANK::SYNC-FEATURES-TO-EMACS))") (9 "((LAMBDA NIL))") (10 "((LAMBDA (SWANK-BACKEND::HOOK SWANK-BACKEND::FUN)) #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA NIL) {1410E8B5}>)") (11 "((LAMBDA NIL))") (12 "((LAMBDA (SWANK-BACKEND::HOOK SWANK-BACKEND::FUN)) #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK> #<FUNCTION (LAMBDA NIL) {13E2D9F5}>)") (13 "(SWANK::CALL-WITH-REDIRECTED-IO #<SWANK::CONNECTION {14004B11}> #<CLOSURE (LAMBDA NIL) {1410E77D}>)") (14 "(SWANK::CALL-WITH-CONNECTION #<SWANK::CONNECTION {14004B11}> #<FUNCTION (LAMBDA NIL) {13E2D9F5}>)") (15 "(SWANK::HANDLE-REQUEST #<SWANK::CONNECTION {14004B11}>)") (16 "(SWANK::CALL-WITH-BINDINGS NIL #<CLOSURE (LAMBDA NIL) {1410E75D}>)") (17 "((FLET SB-THREAD::WITH-MUTEX-THUNK))") (18 "(SB-UNIX::CALL-WITH-LOCAL-INTERRUPTS #<CLOSURE (FLET SB-UNIX::WITH-LOCAL-INTERRUPTS-THUNK) {4D01C2D}> T)") (19 "((FLET SB-UNIX::WITHOUT-INTERRUPTS-THUNK) T)")) Which not only tells us that the error occurs while Slime is updating identation information, we also (quite accidentally) learn that something is amiss: in frame 7 we see "WEBLOCKS-ASD" which is definitely not part of the normal SBCL distribution... and likely there are others as well. Either this is a custom core, or you do have either .sbclrc, or /etc/sbclrc. Additionally, from the MACRO-FUNCTION & LOOKUP frames I can tell that somehow you have, in some package, a symbol whose name is not a string but a number. This is quite an achievement. :) Constructing a bogus symbol like that is not too hard (SAFETY 0 and lying to the compiler can do it), but getting them interned into a package is a lot harder -- I cannot think of a simple mistake that could cause that even in SAFETY 0 code. In other words, something is probably badly wrong with the image even before Slime starts. Where do the extra packages like Weblocks come from? Once you know that, does the same error occur if you start without them? Cheers, -- Nikodemus

2 1

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