[cl-debian] Bug#445299: slime: No LIST-ASDF-SYSTEMS in the SWANK package

Package: slime Version: 1:20070927-2 Severity: important With the new "contrib-based", pluggable SLIME architecture, there seems to be some out-of-sync problems between SLIME and SWANK. A possible solution (I haven't carefully read what SLIEM is expecting, so this is more a sketch than a patch) would be something like: (loop for name being the hash-keys of asdf::*defined-systems* collect name) If I load the slime-asdf extension and try to do ,load-system, this is the result: --- Emacs message byte-code: Lisp connection closed unexpectedly Lisp connection closed unexpectedly: exited abnormally with code 256 --- From *inferior-lisp* READ: "(:emacs-rex (swank:list-asdf-systems) \"COMMON-LISP-USER\" :repl-thread 10) " ;; Event history end. ;; Backtrace: (0 [error printing frame]) (1 [error printing frame]) (2 [error printing frame]) (3 [error printing frame]) (4 [error printing frame]) (5 [error printing frame]) (6 [error printing frame]) (7 [error printing frame]) (8 [error printing frame]) (9 [error printing frame]) (10 [error printing frame]) (11 [error printing frame]) (12 [error printing frame]) (13 [error printing frame]) (14 (COMMON-LISP:READ-FROM-STRING "(:emacs-rex (swank:list-asdf-systems) \"COMMON-LISP-USER\" :repl-thread 10) " T NIL :START 0 :END NIL :PRESERVE-WHITESPACE NIL)) (15 ((COMMON-LISP:LAMBDA NIL))) (16 [error printing frame]) (17 [error printing frame]) (18 (SWANK::READ-FROM-SOCKET-IO)) (19 (SWANK::READ-FROM-EMACS)) (20 ((COMMON-LISP:LAMBDA NIL))) (21 [error printing frame]) (22 [error printing frame]) (23 [error printing frame]) (24 [error printing frame]) (25 [error printing frame]) (26 ((COMMON-LISP:FLET SWANK::HANDLER))) (27 [error printing frame]) (28 (SB-IMPL::SUB-SERVE-EVENT NIL NIL NIL)) (29 (SB-SYS:WAIT-UNTIL-FD-USABLE 0 :INPUT NIL)) (30 [error printing frame]) (31 [error printing frame]) (32 [error printing frame]) (33 [error printing frame]) (34 [error printing frame]) (35 [error printing frame]) (36 [error printing frame]) (37 [error printing frame]) (38 (SB-IMPL::REPL-FUN NIL)) (39 (SB-IMPL::REPL-FUN NIL)) (40 ((COMMON-LISP:LAMBDA NIL))) (41 ((COMMON-LISP:LAMBDA NIL))) (42 [error printing frame]) (43 (SB-IMPL::TOPLEVEL-REPL NIL)) (44 (SB-IMPL::TOPLEVEL-INIT)) (45 ((COMMON-LISP:LABELS SB-IMPL::RESTART-LISP))) ;; Connection to Emacs lost. [ ;; condition: SB-INT:SIMPLE-READER-PACKAGE-ERROR at 36 (line 1, column 36) on #<SB-IMPL::STRING-INPUT-STREAM {AB265F1}>: Symbol "LIST-ASDF-SYSTEMS" not found in the SWANK package. ;; type: SB-INT:SIMPLE-READER-PACKAGE-ERROR ;; encoding: NIL style: :FD-HANDLER dedicated: NIL] -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages slime depends on: ii cl-swank 1:20070927-2 Superior LISP Interaction Mode for ii emacsen-common 1.4.17 Common facilities for all emacsen Versions of packages slime recommends: ii emacs21 [info-browser] 21.4a+1-5.1 The GNU Emacs editor ii info [info-browser] 4.8.dfsg.1-6 Standalone GNU Info documentation -- no debconf information

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Ingvar, Ingvar Mattsson wrote:
With the new "contrib-based", pluggable SLIME architecture, there seems to be some out-of-sync problems between SLIME and SWANK.
Here I was thinking I had fixed most of them :-(.
If I load the slime-asdf extension and try to do ,load-system, this is the result: --- Emacs message byte-code: Lisp connection closed unexpectedly Lisp connection closed unexpectedly: exited abnormally with code 256
Oh cool! I'll investigate this further, but it could be a while before I find a good solution... Groetjes, Peter - -- signature -at- pvaneynd.mailworks.org http://www.livejournal.com/users/pvaneynd/ "God, root, what is difference?" Pitr | "God is more forgiving." Dave Aronson| -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHBT5B11ldN0tyliURArhYAKCcPQ5mGamL9H/X8DQXYt6X+UjsBgCfWnl9 y9HdoZh8FKr8q19CXGoLyJM= =1mc5 -----END PGP SIGNATURE-----

Here's a partial solution (still not perfect, because this only ends up hitting anoter missing function, SWANK:OPERATE-ON-SYSTEM-FOR-EMACS, and that one I haven't successfully made to work): +(defslimefun list-asdf-systems () + (loop for name being the hash-key of asdf::*defined-systems* + collect name)) What I (ideally) want to have back is the "load an ASDF-based system, get a list of warnings, errors, informational wossnames in a tree-based view, with a direct link to where in the source it was signalled from when that is known". I suspect that is a bit more than what I currently have working. However, since it's been in previous versions, I suspect hunting down OPERATE-ON-SYSTEM-FOR-EMACS from there might be Just The Thing. //Ingvar

Your message dated Fri, 26 Oct 2007 05:32:06 +0000 with message-id <E1IlHni-0003Xp-Fp@ries.debian.org> and subject line Bug#445299: fixed in slime 1:20070927-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
participants (4)
-
Ingvar
-
Ingvar Mattsson
-
owner@bugs.debian.org
-
Peter Van Eynde