slime-devel July 2006

slime-devel@common-lisp.net

26 participants
34 discussions

[slime-devel] Bug report: error in process filter: destructure-case failed
by Max Mikhanosha 14 Jul '06

14 Jul '06

When I evaluate something in REPL which produces a lot of rapid output, sometimes I get a message "destructure-case failed: (:WRITE-STRING ... part of the output ...)" in the message area, and the corresponding output is never added to the REPL buffer. This is happens especially often when I use (trace "ENTIRE-PACKAGE") in order to debug something. I can fix the problem by editing slime.el and adding a duplicate case in the slime-dispatch-event function for :WRITE-STRING (in upper case) being the same as :write-string, but thats just fixing the symptom and the underlaying buy in Slime remains. Here is a test case that I can reproduce 100% Emacs: 22.0.51.7-multi-tty (also happened on 21.3) Slime: latest CVS Lisp: SBCL 0.9.13 x86-64 OS: SuSe 10 64bit, 2.6.15-rc6-2-smp kernel Hardware: Dual core Opteron CL-USER> (require 'cl-ppcre) NIL CL-USER> (trace "CL-PPCRE") ... bunch of output listing all functions in CL-PPCRE ... Now just do the following several times: CL-USER> (cl-ppcre::parse-string "a*b+") ... TRACE output here ... You should see the destructure-case failed messages. Note that sometimes its every other invocation, sometimes you have to do it 10 times to get it. Below is a paste from my *Messages* buffer ---------------------- *Messages* ---------------------- error in process filter: destructure-case failed: (:WRITE-STRING " 4: (CL-PPCRE::GREEDY-QUANT #S(CL-PPCRE::LEXER :STR \"a*b+\" :LEN 4 :REG 0 :POS 0 :LAST-POS NIL)) ") error in process filter: slime-dispatch-event: destructure-case failed: (:WRITE-STRING " 6: CL-PPCRE::NEXT-CHAR returned #\\+ ") error in process filter: destructure-case failed: (:WRITE-STRING " 6: CL-PPCRE::NEXT-CHAR returned #\\+ ") error in process filter: destructure-case failed: (:WRITE-STRING " 6: CL-PPCRE::NEXT-CHAR returned #\\+ ") --------------------------------------------------------- Regards, Max

2 2

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 14 Jul '06

14 Jul '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.917 slime/ChangeLog:1.918 --- slime/ChangeLog:1.917 Wed Jul 12 16:30:56 2006 +++ slime/ChangeLog Thu Jul 13 16:09:19 2006 @@ -1,3 +1,8 @@ +2006-07-13 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> + + * swank.lisp (keywords-of-operator): New support function for + writing user-defined `extra-keywords' methods. + 2006-07-11 Helmut Eller <heller(a)common-lisp.net> * swank-allegro.lisp (make-weak-key-hash-table): Use ACL's weak

2 1

[slime-devel] SLIME and sbcl - Lisp connection closed unexpectedly: connection broken by remote peer
by Mathias Dahl 14 Jul '06

14 Jul '06

I get this error when I try to use SLIME with SBCL: Lisp connection closed unexpectedly: connection broken by remote peer That is the Emacs message. In the *inferior-lisp* buffer, this is displayed: -- WARNING: These Swank interfaces are unimplemented: (ACTIVATE-STEPPING CALLS-WHO DISASSEMBLE-FRAME INSPECT-FOR-EMACS SLDB-BREAK-AT-START SLDB-BREAK-ON-RETURN WHO-BINDS WHO-CALLS WHO-MACROEXPANDS WHO-REFERENCES WHO-SETS WHO-SPECIALIZES) T * ;; Swank started at port: 32794. NIL * Process inferior-lisp hangup -- I load slime with a small function of mine: (defun slime-load () (interactive) (add-to-list 'load-path "~/pgm/slime/") ; your SLIME directory ;; (setq inferior-lisp-program "/usr/bin/clisp") ; your Lisp system (setq inferior-lisp-program "/usr/local/bin/sbcl") ; your Lisp system (require 'slime) (slime-setup)) As you can see, I have used CLISP too, and that works (I changed the inferior-lisp-program variable just now and tested). What could be the problem here? When Googling I mostly found issues with sbcl running remotely, which is not an issue in my case. Thanks! /Mathias

2 3

[slime-devel] ,disconnect
by Bill Atkins 13 Jul '06

13 Jul '06

Can someone add a disconnect comma-command that would be equivalent to slime-disconnect? -- Bill Atkins

2 1

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 13 Jul '06

13 Jul '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.916 slime/ChangeLog:1.917 --- slime/ChangeLog:1.916 Sat Jul 1 03:11:31 2006 +++ slime/ChangeLog Wed Jul 12 16:30:56 2006 @@ -1,9 +1,16 @@ +2006-07-11 Helmut Eller <heller(a)common-lisp.net> + + * swank-allegro.lisp (make-weak-key-hash-table): Use ACL's weak + hashtables. + + * swank.asd: Set *source-directory* to the asdf component dir. + 2006-07-01 Luís Oliveira <loliveira(a)common-lisp.net> - * swank-sbcl.lisp (locate-compiler-note): Change first branch to + * swank-sbcl.lisp (locate-compiler-note): Change first branch to handle the changes introduced by the previous patch to swank-compile-string. - + 2006-06-26 Helmut Eller <heller(a)common-lisp.net> * swank-sbcl.lisp (find-definitions): Remove backward

1 0

[slime-devel] filename in COMPILE-STRING-FOR-EMACS
by Taylor R. Campbell 12 Jul '06

12 Jul '06

Is there a reason that `slime-compile-string' sends only the buffer name and directory, but not the actual filename (if there is one), to COMPILE-STRING-FOR-EMACS?

4 3

[slime-devel] Slime/Allegro and make-weak-key-hash-table
by Lynn Quam 12 Jul '06

12 Jul '06

Is there some good reason that the Allegro weak hash-table machinery is not being used in swank-allegro.lisp?

2 2

[slime-devel] SLIME and Allegro
by Gary King 12 Jul '06

12 Jul '06

The current swank-allegro has a number of functions in it that are also defined in swank-backend. E.g. ;;; swank-backend > (definterface call-with-syntax-hooks (fn) > "Call FN with hooks to handle special syntax." > (funcall fn)) ;;; swank-allegro > (defimplementation call-with-syntax-hooks (fn) > (funcall fn)) My guess is that this is just an accident of history. If I don't hear otherwise, I'll clean up the allegro bit and check it in in the next few days. -- Gary Warren King metabang.com [http://www.metabang.com/] (413) 885 9127 * (206) 338-4052 [Fax] gwking on #lisp (occasionally)

1 0

[slime-devel] mixed development environment
by Kamen TOMOV 12 Jul '06

12 Jul '06

I run Emacs on Windows and connect to a Linux CMU-CL. When I execute M-. (edit definition) in a lisp buffer SLIME looks for a non-existing file on the local (windows) machine that actually resides on the remote (Linux) machine. Is there a known solution to this problem, e.g. can SLIME fetch the remote file or my hopes for a mixed development environment are doomed? Thanks! -- Kamen TOMOV

5 6

[slime-devel] swank-loader compatibility with cl-launch (solved)
by Nathan Bird 05 Jul '06

05 Jul '06

This issue goes back a while with a few different proposed fixes. http://common-lisp.net/pipermail/slime-devel/2006-March/004679.html being where I first know about it. This solution is pretty simple, except that it uses functions from the asdf in swank-loader.lisp. Is there anyone using swank-loader directly that does not have asdf and swank properly setup? If asdf is setup properly you can still directly invoke swank-loader. (defvar *source-directory* - (make-pathname :name nil :type nil - :defaults (or *load-pathname* *default-pathname-defaults*)) + (asdf:component-pathname (asdf:find-system :swank)) The reason being that when cl-launch loads the system, it puts the swank-loader.fasl in its own cache, and then when it loads that, the *load-pathname* is apparently nil and it can't find the source files. Slime still puts the fasls in its own cache. With this the source files are always found relative to the location of the asd file, which should be pretty dependable right? I've tested this with ACL on windows loading swank directly. And on debian sbcl loading swank directly, and cl-launch loading swank. Nathan Bird

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel July 2006