[mcclim-devel] ASDF building problems on CMUCL
It seems as if there are some problems with ASDF module specification for scigraph in current versions of McCLIM CVS. When I try to build as per the instructions (using cmucl), the build stalls after loading the module specs and it does not matter whether I load system.lisp or mcclim.asd. A stacktrace is show below. Outcommenting the definition of the scigraph system removes the problem and McCLIM builds and runs without problems. It would thus appear that the scigraph system triggers an infinite loop somewhere in ASDF. The problem appears with todays CVS and the version labelled as McCLIM-0-9-1; it appears that the version McCLIM-0-9 only works with mkdefsystem enabled lisps. I am running on a Debian system with the following versions: ii common-lisp-controller 4.14 ii cmucl 19a-release-20040728-11 ii cl-asdf 1.86-4 0] backtrace 0: (ASDF::PARSE-COMPONENT-FORM NIL (:MODULE "scigraph" :PATHNAME #p"/net/daphne/usr/local/home/tedchly/Tools/ANON-CVS/mcclim/" :DEPENDS-ON ...)) 1: (ASDF::PARSE-COMPONENT-FORM 2 NIL (:MODULE "scigraph" :PATHNAME #p"/net/daphne/usr/local/home/tedchly/Tools/ANON-CVS/mcclim/" :DEPENDS-ON ...))[:EXTERNAL] 2: (LISP::SLOLOAD #<Stream for file "/net/daphne/usr/local/home/tedchly/Tools/ANON-CVS/mcclim/mcclim.asd">) 3: (LISP::INTERNAL-LOAD #p"mcclim.asd" #p"/net/daphne/usr/local/home/tedchly/Tools/ANON-CVS/mcclim/mcclim.asd" :ERROR :SOURCE) 4: (LISP::INTERNAL-LOAD #p"mcclim.asd" #p"/net/daphne/usr/local/home/tedchly/Tools/ANON-CVS/mcclim/mcclim.asd" :ERROR NIL) 5: (LOAD "mcclim.asd" :VERBOSE NIL :PRINT ...) 6: (EXTENSIONS:INTERACTIVE-EVAL (LOAD "mcclim.asd")) 7: (LISP::%TOP-LEVEL) 8: ((LABELS LISP::RESTART-LISP EXTENSIONS:SAVE-LISP)) ------------------------+----------------------------------------------------- Christian Lynbech | christian #\@ defun #\. dk ------------------------+----------------------------------------------------- Hit the philistines three times over the head with the Elisp reference manual. - petonic@hal.com (Michael A. Petonic)
Christian Lynbech <christian.lynbech@ericsson.com> writes:
It seems as if there are some problems with ASDF module specification for scigraph in current versions of McCLIM CVS. [...] McCLIM-0-9-1; it appears that the version McCLIM-0-9 only works with mkdefsystem enabled lisps.
I confirm this. Paolo -- Lisp Propulsion Laboratory log - http://www.paoloamoroso.it/log
sorry, I have not idea what mcclim does with German Umlauts. I'm using sbcl with :sb-unicode in the *features* list but if there e.g a ä or even a § in a text, I will be thrown into the debugger. What do I have to do to make Umlauts running with SBCL? Regards Friedrich
Friedrich Dominicus <frido@q-software-solutions.de> writes:
sorry, I have not idea what mcclim does with German Umlauts. I'm using sbcl with :sb-unicode in the *features* list but if there e.g a ä or even a § in a text, I will be thrown into the debugger.
On the assumption that you're using the CLX backend, I think the relevant piece of code is the default :TRANSLATE function in clx.
What do I have to do to make Umlauts running with SBCL?
Take a look at translate.lisp in climacs CVS, and see if that can be adapted to your needs. (Note: the issue is more complex than this simple "solution" might imply. I'm assuming that you don't actually want to think about the complexity of managing font sets with differing encodings, but please don't let me stop you.) Cheers, Christophe
Christophe Rhodes <csr21@cam.ac.uk> writes:
Friedrich Dominicus <frido@q-software-solutions.de> writes:
sorry, I have not idea what mcclim does with German Umlauts. I'm using sbcl with :sb-unicode in the *features* list but if there e.g a À or even a § in a text, I will be thrown into the debugger.
On the assumption that you're using the CLX backend, I think the relevant piece of code is the default :TRANSLATE function in clx. Yes I use CLX and I found the relevant pieces e.g: #-unicode (defun translate (src src-start src-end afont dst dst-start) ;; This is for replacing the clx-translate-default-function
but also ; Yes, the following is a nasty hack. ; It's just a proof of concept, I'll try not to commit it :] ; If it does get committed, it shouldn't affect anyone much... #+unicode (defun translate (source source-start source-end initial-font destination destination-start) ; do the first character especially (let* ((code (char-code (char source source-start))) (result (fontset-point code))) in medium.lisp in McCLIM/Backends/CLX/ well my featurs list says that :sb-unicode is part of it but not :unicode. However something is there and I'm now wondering: a) wether to use it b) if that is sufficient
What do I have to do to make Umlauts running with SBCL?
Take a look at translate.lisp in climacs CVS, and see if that can be adapted to your needs.
Must be sitting around here somewhere.
(Note: the issue is more complex than this simple "solution" might imply. I'm assuming that you don't actually want to think about the complexity of managing font sets with differing encodings, but please don't let me stop you.)
I was afraid that that's the case and asked therefor if someone more in "CLIM" has an idea. I'm just starting to learn it and well at the moment I have a rough understanding on how it works. But there are so many functions, macros etc, that it's a long way to go till I get a base understanding... Besides it seems that McCLIM /= CLIM in some aspects. Just one example this compiles and works in McCLIM (define-command-table file-menu :inherit-from '(user-command-table) :menu (("Load" :command com-load-account) ("Quit" :command com-quit-application))) but LWs CLIM accepts that too but while starting the application I got: (main) Error: Command table NIL not found 1 (abort) Return to level 0. 2 Return to top loop level 0. That's really encouriging, because: (find-command-table 'USER-COMMAND-TABLE) #<STANDARD-COMMAND-TABLE USER-COMMAND-TABLE 21F0D66C> but of course something here might be wrong for LW-CLIM (define-application-frame clim-account () ((current-account :initform nil :accessor current-account) (interaction-pane)) (:pointer-documentation :t) (:menu-bar (("File" :menu file-menu))) (:panes (interactor :interactor) (actual-account :application :incremental-redisplay t :display-function #'display-current-account) (accounts :application :incremental-redisplay t :display-function #'display-accounts)) (:layouts (default (vertically () (horizontally () actual-account accounts) interactor)))) which seems to be fine for McCLIM. So the C in CLIM seems to be a overoptimistic.... but that's a different story.... Regards Friedrich
"FD" == Friedrich Dominicus <frido@q-software-solutions.de> writes:
FD> What do I have to do to make Umlauts running with SBCL? I have a similar question: How to input accented characters with SBCL and CLX backend? When I type an accented character in a McCLIM input field, nothing happens. I can see there's some support in Backends/CLX/keysym*.lisp, but how to make it work? Thanks for any clue. Regards, Milan Zamazal -- I think any law that restricts independent use of brainpower is suspect. -- Kent Pitman in comp.lang.lisp
participants (5)
-
Christian Lynbech -
Christophe Rhodes -
Friedrich Dominicus -
Milan Zamazal -
Paolo Amoroso