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