Re: [STUMP] Stumpwm and clisp

[Philippe Brochard]

Xavier Maillard writes:

> Hello,
>
Hello :)

> I finally got clisp 2.38 installed and running on my system with clx/new-clx
> module.
>
> I, then, decided it was time to try it out with stumpwm and I did as Philippe
> Brochard told me in a private mail.
>
> And here are my problems :) (Note that Philippe is not to blame here :)).
>
> So I loaded clisp and tried to load stumpwm. Here all is ok.
>
> Then, I tried this:
>
> (stumpwm:stumpwm ":1")
>
> (Wanted to launch in a nested session) and this is what I got:
>
> *** - FUNCALL: undefined function XLIB:CHARACTER->KEYSYMS
> Rentrées possibles:
> USE-VALUE      :R1      You may input a value to be used instead of 
> (FDEFINITION 'XLIB:CHARACTER->KEYSYMS).
> RETRY          :R2      Reéssayer
> STORE-VALUE    :R3      You may input a new value for (FDEFINITION 
> 'XLIB:CHARACTER->KEYSYMS).
> ABORT          :R4      ABORT
> RETRY          :R5      Retry performing #<ASDF:COMPILE-OP NIL #x2046800E> on 
> #<ASDF:CL-SOURCE-FILE "package" #x2046097E>.
> ACCEPT         :R6      Continue, treating #<ASDF:COMPILE-OP NIL #x2046800E> 
> on #<ASDF:CL-SOURCE-FILE "package" #x2046097E> as having been successful.
> ABORT          :R7      ABORT
> RETRY          :R8      Retry performing #<ASDF:COMPILE-OP NIL #x20461C66> on 
> #<ASDF:CL-SOURCE-FILE "package" #x2046097E>.
> ACCEPT         :R9      Continue, treating #<ASDF:COMPILE-OP NIL #x20461C66> 
> on #<ASDF:CL-SOURCE-FILE "package" #x2046097E> as having been successful.
> ABORT          :R10     ABORT
> Break 3 [6]> 
>
For this, Magnus Henoch on the clisp ML tell me to do like this:

----------------------------------------------------------------------
(defun character->keysym (ch)
  "Convert a char to a keysym"
  ;; XLIB:CHARACTER->KEYSYMS should probably be implemented in NEW-CLX
  ;; some day.  Or just copied from MIT-CLX or some other CLX
  ;; implementation (see translate.lisp and keysyms.lisp).  For now,
  ;; we do like this.  It suffices for modifiers and ASCII symbols.
  #-clisp (first (xlib:character->keysyms ch))
  #+clisp (case ch
            (:character-set-switch #xFF7E)
            (:left-shift #xFFE1)
            (:right-shift #xFFE2)
            (:left-control #xFFE3)
            (:right-control #xFFE4)
            (:caps-lock #xFFE5)
            (:shift-lock #xFFE6)
            (:left-meta #xFFE7)
            (:right-meta #xFFE8)
            (:left-alt #xFFE9)
            (:right-alt #xFFEA)
            (:left-super #xFFEB)
            (:right-super #xFFEC)
            (:left-hyper #xFFED)
            (:right-hyper #xFFEE)
            (t
             (etypecase ch
               (character
                ;; Latin-1 characters have their own value as keysym
                (if (< 31 (char-code ch) 256)
                    (char-code ch)
                  (error "Don't know how to get keysym from ~A" ch)))))))
----------------------------------------------------------------------


Then I got clisp/new-clx working but there is something strange with
the xlib:ungrab-pointer, the *display* change a lot after a call to
it. But I haven't got reply for this request.

> I am almost as n00b in clisp as I am in python and thus I really do not know
> what is going on.
>
> Maybe I need to tell clisp to load clx or something like that.
>
I think it's the new-clx the cause of this trouble.

Try with the mit-clx, it works really fine.

[...]

Philippe

-- 
Philippe Brochard    <address@hidden>
                      http://hocwp.free.fr

-=-= http://www.gnu.org/home.fr.html =-=-