slime-devel July 2009

slime-devel@common-lisp.net

23 participants
41 discussions

[slime-devel] [PATCH] Fix ECL under MacPorts (ecl-0.9l)
by Mark Evenson 27 Jul '09

27 Jul '09

MacPorts has an older version of ECL (ecl-0.9l) that doesn't have the EXT:+ECL-VERSION-NUMBER+ causing SLIME to fail to load. The attached diff fixes this by checking for the existence of the symbol in 'swank-ecl.lisp' at read-time. I'll file a ticket with MacPorts to try to update the port. Mark -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."

2 1

[slime-devel] using chinese characters in SLIME
by Andrew Webb 26 Jul '09

26 Jul '09

I'm having problems with this UTF-8 encoded file, as per log below. The file can be displayed by emacs, so MULE is OK (if that's relevant). What you see here is NOT what I get if I enter the same code directly into the native lisp REPL (outside emacs). Coding-system & net-coding system are both utf8 - any ideas? I'm new (very) at lisp/emacs/slime, but it seems to be a slime-related issue. Emacs 22.3, CLisp 2.47 Log: ;; Swank started at port: 3839. CL-USER> (with-open-file (infile "d:/backup/my documents/personal/wode.u8.txt") (read infile)) .\346\210\221\347\232\204 CL-USER>

2 1

[slime-devel] CCL changes
by Gail Zacharias 26 Jul '09

26 Jul '09

Hello, I'm about to check in a slew of changes to CCL (OpenMCL) to provide better support for Slime. I have a version of the swank backend for CCL modified to use the new functionality, and have been using it for a few weeks without problems so I'd like to submit it for inclusion in slime. However, the swank changes are textually extensive and would be a pain to conditionalize individually, and the versions of ccl without the new stuff are still in common use and probably will be for a few more months. So the approach I've come up with is as follows: - Add a new file, "swank-ccl.lisp", which implements the swank backend for ccl using the new functionality. - Change swank-loader to load swank-ccl rather than swank-openmcl. - The old file, "swank-openmcl.lisp", still exists, but is not loaded by default. - swank-ccl.lisp checks whether it's running in a ccl with the new changes, and if not, switches to swank-openmcl.lisp. Is this acceptable? If not, what would be the best way to proceed? I've attached swank-ccl.lisp to this message, below is the swank-loader change. diff -r1.90 swank-loader.lisp 40c40 < #+openmcl '(metering swank-openmcl swank-gray) --- > #+clozure '(metering swank-ccl swank-gray)

2 1

[slime-devel] How to support a new interpreter?
by Elena Garrulo 24 Jul '09

24 Jul '09

Hello, how would you add to Slime support for another interpreter? AFAIK, that means just writing a dedicated Swank module. By looking at Slime48, the module to support Scheme48 in Slime, there is quite a bit of code involved. Any directions about the required interface? Thanks

3 6

[slime-devel] Daily ChangeLog diff
by Helmut Eller 23 Jul '09

23 Jul '09

Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.228 slime/contrib/ChangeLog:1.229 --- slime/contrib/ChangeLog:1.228 Tue Jul 21 07:02:42 2009 +++ slime/contrib/ChangeLog Wed Jul 22 07:25:28 2009 @@ -1,3 +1,12 @@ +2009-07-22 Stas Boukarev <stassats(a)gmail.com> + + * swank-fuzzy.lisp (fuzzy-convert-matching-for-emacs): format + floats on the lisp side, because Emacs doesn't accept d0 or s0, + which could get there as a result of *read-default-float-format* + modification. + + * slime-fuzzy.el (slime-fuzzy-insert-completion-choice): ditto. + 2009-07-15 Tobias C. Rittweiler <tcr(a)freebits.de> * swank-sbcl-exts.lisp (compute-enriched-decoded-arglist): Filter

1 0

[slime-devel] Restart Frame on Clozure
by Terje Norderhaug 22 Jul '09

22 Jul '09

Frame-restartable-p is not defined in openmcl-swank.lisp and thus always returns NIL. This seems like an omission given that return- from-frame and restart-frame recently were added: +2009-05-17 Helmut Eller <heller(a)common-lisp.net> + * swank-openmcl.lisp + (return-from-frame, restart-frame) -- Terje Norderhaug

5 14

[slime-devel] Daily ChangeLog diff
by Helmut Eller 22 Jul '09

22 Jul '09

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1812 slime/ChangeLog:1.1813 --- slime/ChangeLog:1.1812 Wed Jul 15 16:34:09 2009 +++ slime/ChangeLog Tue Jul 21 14:34:54 2009 @@ -1,3 +1,9 @@ +2009-07-21 Stas Boukarev <stassats(a)gmail.com> + + * slime.el (slime-sexp-at-point-for-macroexpansion): use markers + for bounds, because in some situations text layout could be modified + before bounds would be used, for example, using keyboard macros. + 2009-07-15 Stas Boukarev <stassats(a)gmail.com> * slime.el (slime-inspector-fetch-all): new command, bound to > Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.226 slime/contrib/ChangeLog:1.228 --- slime/contrib/ChangeLog:1.226 Wed Jul 15 15:37:25 2009 +++ slime/contrib/ChangeLog Tue Jul 21 07:02:42 2009 @@ -3,6 +3,15 @@ * swank-sbcl-exts.lisp (compute-enriched-decoded-arglist): Filter uninteresting arguments for SB-ASSEM:INST. +2009-07-21 Helmut Eller <heller(a)common-lisp.net> + + * swank-goo.goo, swank-jolt.k (create-repl): Implemented. + +2009-07-19 Helmut Eller <heller(a)common-lisp.net> + + * swank-kawa.scm (operator-arglist): Implemented, at least for + some kind of function. + 2009-07-12 Helmut Eller <heller(a)common-lisp.net> * swank-kawa.scm (swank-writer): Use set! for now, as the svn

1 0

[slime-devel] SLIME writing repeatedly on closed streams. (LOG-OUTPUT on Lispworks)
by Madhu 20 Jul '09

20 Jul '09

Here is another situation, this time with LOG-OUTPUT on Lispworks. On Lispworks, when calling CREATE-SERVER is called from the IDE, *LOG-OUTPUT* gets initialized to the listener pane's output stream. When this listener goes away, (say the window is closed), *LOG-OUTPUT* points to a non-existant stream, and subsequently writing to this stream causes errors. (On LWL this can eventually crash the lisp process). [This dept. (logging errors incorrectly) has been a source of headaches for me for a long time. The changes in code the dept. have only made maintaining workarounds more difficult, and have not satisfactorily addressed the failure modes (under which it fails). I suggest that Slime should report error-producing errors only on a file stream over which it has total control.] -- Madhu

1 0

[slime-devel] *STANDARD-OUTPUT* going to *inferior-lisp*
by graham＠gorgeous.org 17 Jul '09

17 Jul '09

*STANDARD-OUTPUT* of functions called from the REPL is going to *inferior-lisp* not to the REPL as it used to. I noticed this when calling DISASSEMBLE; the disassembly appears in the *inferior-lisp* buffer. I'm using SBCL 1.0.29 on Windows with SLIME 2009-06-29. This behaviour was introduced well before today, though I haven't done the usual CVS binary search to find out when. I'm open to the idea that this is not a general problem and that something in my setup is screwing with SLIME, but what could it be? Thanks in advance as usual, Graham

4 7

[slime-devel] Daily ChangeLog diff
by Helmut Eller 16 Jul '09

16 Jul '09

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1811 slime/ChangeLog:1.1812 --- slime/ChangeLog:1.1811 Sun Jul 12 04:01:28 2009 +++ slime/ChangeLog Wed Jul 15 16:34:09 2009 @@ -1,3 +1,13 @@ +2009-07-15 Stas Boukarev <stassats(a)gmail.com> + + * slime.el (slime-inspector-fetch-all): new command, bound to > + in the inspector buffer. + + * doc/slime.texi (Frame Navigation): add description + of `sldb-end-of-backtrace' and `sldb-beginning-of-backtrace'. + (Inspector): add `slime-inspector-fetch-all'. + + 2009-07-12 Helmut Eller <heller(a)common-lisp.net> * slime.el (slime-editing-keys): Don't override M-*. The default Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.225 slime/contrib/ChangeLog:1.226 --- slime/contrib/ChangeLog:1.225 Sun Jul 12 04:01:19 2009 +++ slime/contrib/ChangeLog Wed Jul 15 15:37:25 2009 @@ -1,3 +1,8 @@ +2009-07-15 Tobias C. Rittweiler <tcr(a)freebits.de> + + * swank-sbcl-exts.lisp (compute-enriched-decoded-arglist): Filter + uninteresting arguments for SB-ASSEM:INST. + 2009-07-12 Helmut Eller <heller(a)common-lisp.net> * swank-kawa.scm (swank-writer): Use set! for now, as the svn

1 0

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 2009