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

[slime-devel] Standard output no longer appears in REPL
by Steven E. Harris 25 Jun '11

25 Jun '11

It's been a couple of months since I last used SLIME. Today I noticed that when I evaluate expressions in the REPL that write to *standard-output*, the output appears in the *inferior-lisp* buffer, but not in the REPL as it used to. I'm using GNU Emacs on Windows atop the CLISP Cygwin build. SLIME is up to date with CVS. Is there some new configuration required to restore the old behavior with output streams feeding into the REPL output? -- Steven E. Harris

5 12

[slime-devel] Proposed patch for asdf-loading under ALLEGRO
by Robert Goldman 05 Jan '10

05 Jan '10

ASDF operations using SLIME and SWANK won't work under Allegro's Modern (case-sensitive) lisp, because the symbol names are not in all caps as in ANSI lisp. Here's a small patch that makes it work under ACL mlisp as well as under normal ANSI lisps: Index: swank-asdf.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/contrib/swank-asdf.lisp,v retrieving revision 1.7 diff -b -u -F '^(def' -r1.7 swank-asdf.lisp --- swank-asdf.lisp 23 Oct 2008 21:28:03 -0000 1.7 +++ swank-asdf.lisp 25 May 2009 16:40:10 -0000 @@ -26,7 +26,9 @@ (defun operate-on-system (system-name op Example: \(operate-on-system \"SWANK\" \"COMPILE-OP\" :force t)" (with-compilation-hooks () - (let ((operation (find-symbol operation-name :asdf))) + (let ((operation (or (find-symbol operation-name :asdf) + #+allegro + (find-symbol (string-downcase operation-name) :asdf)))) (when (null operation) (error "Couldn't find ASDF operation ~S" operation-name)) (apply #'asdf:operate operation system-name keyword-args))))

2 1

Re: [slime-devel] random returning the same value
by Tobias C. Rittweiler 30 Nov '09

30 Nov '09

Patrick May <pjm(a)spe.com> writes: > Hi, > > I'm using Slime in Aquamacs with CCL. When I evaluate (random > 100) repeatedly in CCL started from a shell, I get a randomly > generated number between 0 and 99 inclusive. When I do the same with > C-x C-e within Slime, I get the same number every time. (random 100 > (make- > random-state)) gives the same behavior, but (random 100 (make-random- > state t)) works properly. > > Is Slime caching something or have I hosed up my environment? Sorry for the late response. CCL's swank backend uses threads by default, and threads inherit values from the global environment. *RANDOM-STATE* probably becomes thread-local automatically in CCL, resulting in the behaviour you described. It should work when you type in the form at the Slime REPL which evaluates all forms in the same thread. -T.

4 4

[slime-devel] Error in `post-command-hook' ?
by Alberto Riva 21 Aug '09

21 Aug '09

I recently upgraded Slime, and now I keep getting these very annoying warnings, usually when I do something in the modeline, but also at other apparently random times: (1) (error/warning) Error in `post-command-hook' (setting hook to nil): (wrong-type-argument natnump t) If I turn debug on, this is what I get: Debugger entered--Lisp error: (wrong-type-argument natnump t) signal(wrong-type-argument (natnump t)) set-itimer-restart(("run-with-idle-timer<2>" 0.2 0.2 eldoc-print-current-symbol-info t t nil (19018 24548 646301)) t) timer-set-idle-time(("run-with-idle-timer<2>" 0.2 0.2 eldoc-print-current-symbol-info t t nil (19018 24548 646301)) 0.2 t) eldoc-schedule-timer() I'm using Allegro CL 8.1 and XEmacs 21.4.21. I also observed the problem that was reported here earlier: slime-bug("Caught error during fontification while searching for forms that are suppressed by reader-conditionals. The error was: (cl-assertion-failed (<= (point) limit)) but I was able to stop XEmacs doing whatever it was doing with C-g before it ran out of memory. Thanks, Alberto

2 1

[slime-devel] slime-typeout-frame vs autodoc timers
by Raymond Toy 14 Aug '09

14 Aug '09

I finally upgraded to a recent version of slime (2009-07-01 or so) and found a couple of issues. First, I use slime-typeout-frame and it references slime-autodoc-start-timer (and other autodoc stuff). These don't seem to exist anymore. Second, I get the following error using xemacs 21.5.29. These issues prevent me from using the current version. And many thanks for making slime soooo useful, Ray Slime error: (slime,warning/warning) "s-code.lisp":8753:19 (pt=331319). Caught error during fontification while searching for forms that are suppressed by reader-conditionals. The error was: (cl-assertion-failed (<= (point) limit)). This is a bug in Slime itself. Please report this to the mailinglist slime-devel(a)common-lisp.net and include your Emacs version, the guilty Lisp source file, the header of this message, and the following backtrace. Backtrace: backtrace() (let ((standard-output standard-output)) (backtrace)) (let ((standard-output ...)) (let (...) (backtrace)) (with-current-buffer standard-output (prog1 ... ...))) (with-output-to-string (backtrace)) (slime-display-warning "%S:%d:%d (pt=%d).\n%s\n\nThis is a bug in Slime itself. Please report this to the\nmailinglist slime-devel(a)common-lisp.net and include your Emacs\nversion, the guilty Lisp source file, the header of this\nmessage, and the following backtrace.\n\nBacktrace:\n%s\n--------------------------------------------------------------\n" (buffer-name) (line-number-at-pos) (current-column) (point) (apply (function format) message args) (with-output-to-string (backtrace))) slime-bug("Caught error during fontification while searching for forms\nthat are suppressed by reader-conditionals. The error was: %S." (cl-assertion-failed (<= (point) limit))) byte-code("..." [condition result nil slime-bug "Caught error during fontification while searching for forms\nthat are suppressed by reader-conditionals. The error was: %S."] 3) slime-search-suppressed-forms(331141) font-lock-fontify-keywords-region(330036 331141 nil) font-lock-default-fontify-region(330036 331141 nil) font-lock-fontify-region(330036 331141) lazy-shot-fontify-internal(#<buffer "s-code.lisp"> 330036 331064 t "stealthy ") lazy-shot-lock-extent(#<destroyed extent> t) lazy-shot-stealth-lock(#<buffer "s-code.lisp">) apply(lazy-shot-stealth-lock #<buffer "s-code.lisp">) byte-code("..." [this-command inhibit-quit quit-flag match-data itimer current-itimer match-data ((store-match-data match-data)) nil itimer-uses-arguments apply itimer-function itimer-function-arguments last-event-time next-wakeup itimers time-elapsed] 5) itimer-run-expired-timers(0.001288) itimer-timer-driver(nil) ("execute_internal_event()" "[internal]") (dispatch-event "[internal]")

7 11

[slime-devel] Daily ChangeLog diff
by Helmut Eller 02 Aug '09

02 Aug '09

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1813 slime/ChangeLog:1.1817 --- slime/ChangeLog:1.1813 Tue Jul 21 14:34:54 2009 +++ slime/ChangeLog Mon Jul 27 00:08:41 2009 @@ -1,3 +1,33 @@ +2009-07-27 Geo Carncross <geocar(a)gmail.com> + + * swank-ecl.lisp: Support for older ECL installs + from patch by Mark Evenson + +2009-07-26 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-maybe-show-compilation-log): New function. + (slime-compilation-finished-hook): Use it. Now that the + compilation buffer gets not selected it's more acceptable to + display it more often. + (slime-insert-compilation-log): Set compilation-skip-threshold to + 0 and compilation-skip-to-next-location to nil. Seems to work + better for us. + (slime-with-popup-buffer): Synch window-point, otherwise it be at + the end of the buffer for reused buffers. + (slime-display-popup-buffer): Return the window. + +2009-07-26 Helmut Eller <heller(a)common-lisp.net> + + * swank-sbcl.lisp (tempnam): Muffle efficiency notes. + +2009-07-26 Gail Zacharias <gz(a)clozure.com> + + * swank-ccl.lisp: New file. An updated version of + swank-openmcl.lisp in preparation for a slew of changes to CCL and + to honor the new name. + + * swank-loader.lisp (*sysdep-files*): Use it. + 2009-07-21 Stas Boukarev <stassats(a)gmail.com> * slime.el (slime-sexp-at-point-for-macroexpansion): use markers

2 5

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

31 Jul '09

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1819 slime/ChangeLog:1.1821 --- slime/ChangeLog:1.1819 Tue Jul 28 11:03:41 2009 +++ slime/ChangeLog Thu Jul 30 19:27:05 2009 @@ -1,3 +1,15 @@ +2009-07-30 Stas Boukarev <stassats(a)gmail.com> + + * doc/slime.texi (Setting up pathname translations): add that it is + in the `slime-tramp' contrib. + +2009-07-30 Tobias C. Rittweiler <tcr(a)freebits.de> + + * swank-clisp.lisp: Clisp 2.48 experimentally supports threads. So + add infrastructure to use threads in Clisp's swank backend. We do + not make it the default, because it's not prime time yet. There + are still problems with GC, weak-pointers, and thread objects. + 2009-07-28 Stas Boukarev <stassats(a)gmail.com> * doc/slime.texi (slime-selector): mention t and c keys.

1 0

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

29 Jul '09

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1818 slime/ChangeLog:1.1819 --- slime/ChangeLog:1.1818 Mon Jul 27 09:08:16 2009 +++ slime/ChangeLog Tue Jul 28 11:03:41 2009 @@ -1,3 +1,7 @@ +2009-07-28 Stas Boukarev <stassats(a)gmail.com> + + * doc/slime.texi (slime-selector): mention t and c keys. + 2009-07-27 Stas Boukarev <stassats(a)gmail.com> * swank-ccl.lisp (source-note-to-source-location): keys of

1 0

[slime-devel] Tracing Swank/Slime protocol?
by Elena Garrulo 28 Jul '09

28 Jul '09

Hi, in order to develop a new Swank front end, I'd like to understand how such a module interacts with Slime. Since such protocol seems to be undocumented - isn't it? - I think that I could trace Swank from/to Slime communication for an already functional module. Is such an operation already available? Thanks

4 3

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

28 Jul '09

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1817 slime/ChangeLog:1.1818 --- slime/ChangeLog:1.1817 Mon Jul 27 00:08:41 2009 +++ slime/ChangeLog Mon Jul 27 09:08:16 2009 @@ -1,3 +1,9 @@ +2009-07-27 Stas Boukarev <stassats(a)gmail.com> + + * swank-ccl.lisp (source-note-to-source-location): keys of + *temp-file-map* are pathnames, not namestrings; convert + namestrings to pathnames before looking up. + 2009-07-27 Geo Carncross <geocar(a)gmail.com> * swank-ecl.lisp: Support for older ECL installs

1 0

[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

[slime-devel] Slime and ECL
by Matthew Mondor 14 Jul '09

14 Jul '09

Hello, I was unsure to which of the lists this belonged best so I posted it to both slime-devel and ecls-list (if I understand, swank which is part of slime handles the implementation-specifics)... Is slime known to be broken with ECL? I initially tried with ECL 8.12.0 and first had an unknown utf8-unix external format error (so I adapted my ~/.emacs to temporarily not use utf-8 mode, which helped). Then there was another error related to missing ext:+ecl-version-number+ constant (which I could declare in ~/.eclrc, which also helped). However, there then was another error: "Wrong number of arguments passed to function #<compiled-function SI:IHS-TOP>". I then tried using ECL 9.6.0 (or .1? the ecl-9.6.0 archive had a directory named ecl-9.6.1), built with unicode support. The utf8 related error still occurs when utf8 mode is enabled, the +ecl-version-number+ constant is already defined this time, yet the ihs-top function being called with the wrong number of arguments still occurs. Backtrace: > LAMBDA > swank-backend:call-with-debugger-hook > swank:swank-debugger-hook > lambda > swank-backend:call-with-debugger-hook > lambda > swank::call-with-bindings > swank::call-with-connection > swank::simple-serve-requests > swank::serve-requests > swank::serve-connection > swank::serve > swank::setup-server > swank:start-server > si:bytecodes [Evaluation of: (progn (load "/home/mmondor/emacs-scripts/slime/swank-loader.lisp" :verbose t) (funcall (read-from-string "swank-loader:init")) (funcall (read-from-string "swank:start-server") "/tmp/slime.9787" :coding-system "iso-latin-1-unix"))] > si:bytecodes [Evaluation of: (si:top-level)] My experience with slime and ecl is limited, I used to use it with SBCL only previously. The reason why my initial tries were with ECL 8.12 was because I got it working properly with threads, when the bootstrap ecl_min appears to segfault and its signal handler stuck in an endless loop when I try to build 9.6.0/1 with threading support (it builds fine non-threaded). But this is another matter which I didn't spend time to debug yet. :) Thanks, -- Matt

3 4

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

13 Jul '09

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1810 slime/ChangeLog:1.1811 --- slime/ChangeLog:1.1810 Sat Jul 11 14:25:59 2009 +++ slime/ChangeLog Sun Jul 12 04:01:28 2009 @@ -1,3 +1,8 @@ +2009-07-12 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-editing-keys): Don't override M-*. The default + binding should do what Matthias wants. + 2009-07-11 Matthias Koeppe <mkoeppe(a)math.ucdavis.edu> * swank-backend.lisp (definterface): Fix typo in error message. Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.223 slime/contrib/ChangeLog:1.225 --- slime/contrib/ChangeLog:1.223 Sat Jul 11 15:20:18 2009 +++ slime/contrib/ChangeLog Sun Jul 12 04:01:19 2009 @@ -1,3 +1,15 @@ +2009-07-12 Helmut Eller <heller(a)common-lisp.net> + + * swank-kawa.scm (swank-writer): Use set! for now, as the svn + version has problems to resolve setLength. + (<faked-frame>:init): Don't forget the self slot. + +2009-07-12 Helmut Eller <heller(a)common-lisp.net> + + * swank-mit-scheme.scm (swank:create-repl): Implement it. + * swank-kawa.scm, swank-goo.scm, swank.rb (frame-source-location): + Renamed from frame-source-location-for-emacs. + 2009-07-11 Stas Boukarev <stassats(a)gmail.com> * slime-parse.el (slime-make-form-spec-from-string):

2 1

[slime-devel] Binding of M-* wrong
by Matthias Koeppe 12 Jul '09

12 Jul '09

The current SLIME binding of M-* is slime-edit-definition, but it should be slime-pop-find-definition-stack, in analogy to the standard Emacs binding of M-* to pop-tag-mark. This seems to be the change that caused it, probably just a typo. 2009-01-16 Helmut Eller <heller(a)common-lisp.net> * slime.el (slime-keys): Put C-c C-i and M-* back. Could someone please fix it? Thanks, Matthias -- Matthias Koeppe -- http://www.math.ucdavis.edu/~mkoeppe

2 1

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

12 Jul '09

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1808 slime/ChangeLog:1.1810 --- slime/ChangeLog:1.1808 Mon Jul 6 08:32:12 2009 +++ slime/ChangeLog Sat Jul 11 14:25:59 2009 @@ -1,3 +1,12 @@ +2009-07-11 Matthias Koeppe <mkoeppe(a)math.ucdavis.edu> + + * swank-backend.lisp (definterface): Fix typo in error message. + +2009-07-11 Stas Boukarev <stassats(a)gmail.com> + + * doc/Makefile (clean): Remove bash extensions. Patch by + Teemu Likonen. + 2009-07-06 Tobias C. Rittweiler <tcr(a)freebits.de> * swank-ecl.lisp (find-external-format): Copied from @@ -79,7 +88,7 @@ 2009-06-25 Geo Carncross <geocar(a)gmail.com> - * swank-ecl.lisp: Profiling support by Marko Kocić + * swank-ecl.lisp: Profiling support by Marko Koci? 2009-06-27 Helmut Eller <heller(a)common-lisp.net> Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.222 slime/contrib/ChangeLog:1.223 --- slime/contrib/ChangeLog:1.222 Sat Jul 4 05:54:16 2009 +++ slime/contrib/ChangeLog Sat Jul 11 15:20:18 2009 @@ -1,3 +1,9 @@ +2009-07-11 Stas Boukarev <stassats(a)gmail.com> + + * slime-parse.el (slime-make-form-spec-from-string): + set syntax table to lisp-mode-syntax-table in a temporary buffer. + Necessary for some parsing functions to work correctly. + 2009-07-04 Tobias C. Rittweiler <tcr(a)freebits.de> Fix font-lock magic for s-code.lisp in the series package.

1 0

[slime-devel] Who uses slime-complete-form (C-c C-s)?
by Tobias C. Rittweiler 11 Jul '09

11 Jul '09

I'd like to remove C-c C-s. This would remove a good chunk of code, and would make some other code more straightforward. Disclaimer: I do use C-c C-s myself to automatically insert the situation keywords for EVAL-WHEN forms but I could live without that. -T.

6 5