- slime-devel - mailman3.common-lisp.net

[slime-devel] Daily ChangeLog diff
by Helmut Eller 10 Oct '10

10 Oct '10

Index: slime/ChangeLog diff -u slime/ChangeLog:1.2149 slime/ChangeLog:1.2150 --- slime/ChangeLog:1.2149 Fri Oct 8 05:03:24 2010 +++ slime/ChangeLog Sat Oct 9 19:02:32 2010 @@ -1,3 +1,16 @@ +2010-10-09 Raymond Toy <toy.raymond(a)gmail.com> + + * swank-cmucl.lisp (codepoint-length): Implement codepoint-length + to return the number of codepoints in cmucl's utf-16 strings. + + * swank-backend.lisp (:swank-backend): Export codepoint-length. + (codepoint-length): definterface codepoint-length. Default is to + use LENGTH. + + * swank-rpc.lisp (write-message): Call + swank-backend:codepoint-length to get the correct length for + emacs. + 2010-10-08 Christophe Rhodes <csr21(a)cantab.net> Pass more detailed source location information to

1 0

[slime-devel] CMUCL unicode strings breaks slime
by Raymond Toy 10 Oct '10

10 Oct '10

This has been happening for some time, and it's annoying enough that I want to fix it. With CMUCL 20b and slime 2010-09-20, try the following: (defvar *s* (make-string 4)) *s* (setf (lisp:codepoint *s* 0) #x10000)) Upto now, everything is ok. Now print the string: *s* At this point, the string is displayed, with a rectangular box for the codepoint #x10000 followed by two ^@ for the two null characters. (Recall that unicode strings in cmucl are utf-16 strings, so the first two elements of *s* are the surrogate pair for #x10000.) I get an error from xemacs about itimer: itimer "run-at-time<2>" signaled: (wrong-type-argument listp write-string) Wrong type argument: listp, :write-string And *slime-events* buffer is kind of garbled: (:emacs-rex (swank:listener-eval "(print *s*)\n") "COMMON-LISP-USER" :repl-thread 18) (:write-string "\n\"𐀀

3 23

[slime-devel] Daily ChangeLog diff
by Helmut Eller 09 Oct '10

09 Oct '10

Index: slime/ChangeLog diff -u slime/ChangeLog:1.2148 slime/ChangeLog:1.2149 --- slime/ChangeLog:1.2148 Thu Oct 7 13:15:07 2010 +++ slime/ChangeLog Fri Oct 8 05:03:24 2010 @@ -1,3 +1,19 @@ +2010-10-08 Christophe Rhodes <csr21(a)cantab.net> + + Pass more detailed source location information to + swank:compile-string-for-emacs. Motivated by R's source location + needs (where srcrefs are line/column based). + + * slime.el (slime-compile-string): Generate :line location format + from start-offset, passing it through to + swank:compile-file-for-emacs. + (find-definition.2): Use new-style position. + + * swank.lisp (compile-string-for-emacs): Use only the offset from + the position argument. + + * swank-backend.lisp (swank-compile-string): Fix docstring typo. + 2010-10-07 Nikodemus Siivola <nikodemus(a)random-state.net> Hanging on to a *log-output* from a previous image is bad on SBCL

1 0

[slime-devel] contrib for repl images
by Christophe Rhodes 08 Oct '10

08 Oct '10

Hi, Attached are files which I propose to add to contrib/ to allow image display in the repl. The Common Lisp support is entirely non-existent, but I have prototype code using the slime support to do manipulations of graphical objects in R: <http://doc.gold.ac.uk/~mas01cr/tmp/swankr-images.png> displays an example. I'd like to put this or something like it in; I'm asking for review of this approach and implementation. Cheers, Christophe

4 4

[slime-devel] Daily ChangeLog diff
by Helmut Eller 08 Oct '10

08 Oct '10

Index: slime/ChangeLog diff -u slime/ChangeLog:1.2147 slime/ChangeLog:1.2148 --- slime/ChangeLog:1.2147 Sat Oct 2 07:16:54 2010 +++ slime/ChangeLog Thu Oct 7 13:15:07 2010 @@ -1,3 +1,13 @@ +2010-10-07 Nikodemus Siivola <nikodemus(a)random-state.net> + + Hanging on to a *log-output* from a previous image is bad on SBCL + at least: it is initialized to an FD-STREAM, which cannot be + reused from one image to another. + + Deal with this by using sb-ext:*save-hooks* to clear the stream. + + * swank-sbcl.lisp (deinit-log-output): New function. + 2010-10-02 Helmut Eller <heller(a)common-lisp.net> Rename slime-macro/compiler-macro-expand-1 => slime-expand-1

1 0

[slime-devel] Slime presentation marker bug
by Nathan Bird 04 Oct '10

04 Oct '10

I put a test case here that documents it: http://paste.lisp.org/+2GLO The issue is that when it starts a presentation it saves a marker, but then that marker gets moved when printing text and so when it ends the presentation the start and end markers are the same point, the one immediately after the text we are trying to present. I'm not sure where to go from here. I don't know how to get the old marker to stay in place any more than it is now. There is a comment: ;; We use markers because text can also be inserted before this presentation. ;; (Output arrives while we are writing presentations within REPL results.) Perhaps that is more relevant to printing with the target :repl-result vs target null? I tried changing the presentation start function (it's on the paste) to save the number if target is null and that looks like it is mostly working for me, can anyone else comment on the idea? -- Nathan Bird nathan(a)acceleration.net http://www.acceleration.net/ Custom Programming, Design, Hosting, and Broadband.

2 10

[slime-devel] SLIME development newbie questions
by Tamas K Papp 03 Oct '10

03 Oct '10

Hi, I decided that it would be worthwhile to learn some Emacs Lisp, mainly in order to understand the internals of SLIME better -- maybe I could get to the point that I could extend and customize it myself. This is why I am posting here instead of an emacs group. I am looking for help on how to get started, especially with the following: 1. Is there a SLIME-like IDE for Emacs Lisp? If not, what's the closest? I know that Emacs itself provides some functionality, but it does not look nearly as comfy as SLIME for CL. Eg I couldn't figure out the equivalent of M-. and similar. 2. Is there a document describing the architecture of SLIME? 3. How should I start? What's the best way to start poking around in SLIME? Tamas

6 6

[slime-devel] Daily ChangeLog diff
by Helmut Eller 03 Oct '10

03 Oct '10

Index: slime/ChangeLog diff -u slime/ChangeLog:1.2146 slime/ChangeLog:1.2147 --- slime/ChangeLog:1.2146 Fri Oct 1 05:30:43 2010 +++ slime/ChangeLog Sat Oct 2 07:16:54 2010 @@ -1,3 +1,18 @@ +2010-10-02 Helmut Eller <heller(a)common-lisp.net> + + Rename slime-macro/compiler-macro-expand-1 => slime-expand-1 + + * slime.el (slime-expand-1): Renamed from + slime-macro/compiler-macro-expand-1. + (slime-expand-1-inplace): Renamed from + slime-macro/compiler-macro-expand-1-inplace. + + * swank.lisp (swank-expand-1): Renamed from + swank-macro/compiler-macro-expand-1. + (swank-expand): Renamed from swank-macro/compiler-macro-expand. + (expand-1): Renamed from macro/compiler-macro-expand-1. + (expand): Renamed from macro/compiler-macro-expand. + 2010-10-01 Helmut Eller <heller(a)common-lisp.net> Don't use indent-sexp for macroexpanded code.

1 0

[slime-devel] Daily ChangeLog diff
by Helmut Eller 02 Oct '10

02 Oct '10

Index: slime/ChangeLog diff -u slime/ChangeLog:1.2144 slime/ChangeLog:1.2146 --- slime/ChangeLog:1.2144 Wed Sep 22 15:17:35 2010 +++ slime/ChangeLog Fri Oct 1 05:30:43 2010 @@ -1,3 +1,22 @@ +2010-10-01 Helmut Eller <heller(a)common-lisp.net> + + Don't use indent-sexp for macroexpanded code. + indent-sexp is potentially slow and usually redundant. + + * slime.el (slime-initialize-macroexpansion-buffer): Don't use + indent-sexp. + (slime-eval-macroexpand-inplace): Avoid indent-sexp but + use slime-insert-indented. + +2010-10-01 Helmut Eller <heller(a)common-lisp.net> + + Save result in kill ring for M-- C-x C-e. + For C-u C-x C-e set mark before inserting. + + * slime.el (slime-eval-save): New function. + (slime-eval-print): Set mark before inserting. + (slime-interactive-eval): Use it. + 2010-09-22 Stas Boukarev <stassats(a)gmail.com> * swank.lisp (eval-for-emacs): Send (:abort condition) where

1 0

[slime-devel] slime-interactive-eval into kill ring
by Tamas K Papp 01 Oct '10

01 Oct '10

Hi, C-x C-e (slime-interactive-eval) prints the value(s) in the minibuffer. Prefixed with C-u, it is inserted in the current buffer. Is there a way to insert it somewhere else? Ideally, it would be very handy to have a way to just save the result in the kill ring, then I could yank it later. Thanks, Tamas

2 5