>From the code:
;; FIXME: clisp croaks with an 'attempt to use closed display' error
;; when this is called. So skip it. And SBCL needs it called or it
;; will croak with a "another window manager is running" error. arg!
Unfortunately I get the 'attempt to use closed display' error in SBCL
too. Removing the line gives 'another window manager is running' as
described :(
SBCL 1.0.27.debian
telent clx 0.7.3 (not the debian version)
Backtrace attached in case it's any use.
Ben
Attempt to use closed display #<XLIB:DISPLAY :0 (The X.Org Foundation
R10601901)>
0: (SB-DEBUG::MAP-BACKTRACE #<CLOSURE (LAMBDA #) {10041DADF9}>)[:EXTERNAL]
1: (SB-DEBUG:BACKTRACE 100 #<SB-IMPL::STRING-OUTPUT-STREAM {10041DAD51}>)
2: (STUMPWM::BACKTRACE-STRING)
3: (STUMPWM::PERFORM-TOP-LEVEL-ERROR-ACTION #<XLIB:CLOSED-DISPLAY {10041DA381}>)
4: (SIGNAL #<XLIB:CLOSED-DISPLAY {10041DA381}>)[:EXTERNAL]
5: (ERROR XLIB:CLOSED-DISPLAY)[:EXTERNAL]
6: (XLIB::X-ERROR XLIB:CLOSED-DISPLAY)[:EXTERNAL]
7: (XLIB:DISPLAY-FINISH-OUTPUT
#<XLIB:DISPLAY :0 (The X.Org Foundation R10601901)>)
8: (STUMPWM::HANDLE-EVENT)[:EXTERNAL]
9: ((FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK))
10: ((FLET #:WITHOUT-INTERRUPTS-BODY-[CALL-WITH-RECURSIVE-LOCK]477))
11: (SB-THREAD::CALL-WITH-RECURSIVE-LOCK
#<CLOSURE (FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK) {7FA4A3707AB9}>
#S(SB-THREAD:MUTEX
:NAME "CLX Event Lock"
:%OWNER #<SB-THREAD:THREAD "initial thread" RUNNING {10039169D1}>
:STATE 1))
12: (XLIB:PROCESS-EVENT #<XLIB:DISPLAY :0 (The X.Org Foundation
R10601901)>)[:EXTERNAL]
13: (STUMPWM::STUMPWM-INTERNAL-LOOP)
14: (STUMPWM::STUMPWM-INTERNAL ":0.0")
15: (STUMPWM ":0.0")
16: ((LAMBDA ()))
17: ((LABELS SB-IMPL::RESTART-LISP))
_______________________________________________
Stumpwm-devel mailing list
Stumpwm-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/stumpwm-devel
