[STUMP] Re: Stumpwm ECL/SBCL

[A.W.]

I never filed a bug because I don't know where the bug is, but I
suspect it's in stump.
I'm using the git version of stump, so it would be plain rude to
report a bug on the BTS.

SBCL/stump works, but SBCL/Stump/SLIME does not.
what's in my rc:
;Broken currently. Unclear if it's sbcl, swank, or stump that's te problem.
;; (require 'asdf)
;; (asdf:oos 'asdf:load-op 'swank)
;; (swank:start-server :dont-close t)
Before the update to a recent SLIME snapshot swank failed to load on
the latest sbcl. The first two lines now return NIL, but on trying to
start the server it throws:
odd number of &KEY arguments0: (SB-DEBUG::MAP-BACKTRACE #<CLOSURE
(LAMBDA #) {CAA8165}>)[:EXTERNAL]
1: (SB-DEBUG:BACKTRACE 100 #<SB-IMPL::STRING-OUTPUT-STREAM {CAA8111}>)
2: (BACKTRACE-STRING)
3: (ERR "~A")[:EXTERNAL]
4: (EVAL-LINE "(swank:start-server :dont-close t)")
5: (CALL-INTERACTIVELY
 "eval"
 #S(ARGUMENT-LINE
 :STRING "eval (swank:start-server :dont-close t)"
 :START 39))
6: (EVAL-COMMAND "eval (swank:start-server :dont-close t)" NIL)
7: (HANDLE-STUMPWM-COMMANDS #<XLIB:WINDOW :0 67>)
8: (HANDLE-EVENT)[:EXTERNAL]
9: ((FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK))
10: ((FLET #:WITHOUT-INTERRUPTS-BODY-[CALL-WITH-RECURSIVE-LOCK]509))
11: (SB-THREAD::CALL-WITH-RECURSIVE-LOCK
 #<CLOSURE (FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK) {B77FDCB5}>
 #S(SB-THREAD:MUTEX
 :NAME "CLX Event Lock"
 :%OWNER #<SB-THREAD:THREAD "initial thread" RUNNING {B696571}>
 :STATE 1))
12: (XLIB:PROCESS-EVENT #<XLIB:DISPLAY :0 (The X.Org Foundation
R10402000)>)[:EXTERNAL]
13: (STUMPWM-INTERNAL-LOOP)
14: (STUMPWM-INTERNAL ":0")
15: (STUMPWM ":0")
16: ((LAMBDA ()))
17: ((LABELS SB-IMPL::RESTART-LISP))

done with stumpwm-mode

-- TheGZeus: Proof of Ferocious Will --

Message: 9
Date: Tue, 24 Feb 2009 10:27:33 +0100
From: Luca Capello <address@hidden>
Subject: Re: [STUMP] ECL
To: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset="us-ascii"

Hi there!

On Tue, 24 Feb 2009 01:50:59 +0100, A W wrote:
> Considering that we currently have to chooe between
> fast-and-threaded(sbcl(sbcl/slime/stump broken on Sid atm)),

Sorry, but what is exactly the problem on Debian sid?  I cannot find any
bug in the Debian BTS about that:

 http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=sbcl;dist=unstable
 http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=slime;dist=unstable
 http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=stumpwm;dist=unstable

And indeed StumpWM works with SBCL on my Debian sid (just tried, I use
CLISP instead).

> Fuck, packagers could make a stumpwm-ecl binary, compiled with
> gcc.(need to research if the binaries strip symbols)

This point is discussed every now and then and I clearly stated, with my
StumpWM Debian maintainer hat on, that I will never do it.

Thx, bye,
Gismo / Luca