slime-devel September 2009

slime-devel@common-lisp.net

26 participants
46 discussions

[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] slime-lispworks.el 2009-09-02 regression
by Madhu 25 Oct '09

25 Oct '09

This commit introduces a regression: * 2009-09-02 Stas Boukarev <stassats(a)gmail.com> | | * swank-lispworks.lisp (replace-strings-with-symbols): New | function for recursively interning and replacing strings in a | list. (arglist): Replace all strings in arglists with symbols. For a test case, consider what LW returns for (function-lambda-list 'with-foo) for a definition like (defmacro with-foo ((var . args) &body body) `(let ((,var ,@args)) ,@body)) -- Madhu

3 3

[slime-devel] SLIME+SBCL+WIN32
by Luke J Crook 05 Oct '09

05 Oct '09

I've been getting the following slime error from CVS using SBCL 1.0.29 for win32 in Emacs; See also: The ANSI Standard, Macro DEFPACKAGE ; compiling file "c:\\home\\bin\\central-registry\\slime\\swank-source-path- parser.lisp" (written 25 JUN 2009 08:23:18 PM): ; c:\home\.slime\fasl\2009-09-24\sbcl-1.0.29-win32-x86\swank-source-path- parser.fasl written ; compilation finished in 0:00:00.125 ; loading #P"c:\\home\\.slime\\fasl\\2009-09-24\\sbcl-1.0.29-win32-x86\\swank- source-path-parser.fasl" ; compiling file "c:\\home\\bin\\central-registry\\slime\\swank-source-file- cache.lisp" (written 15 MAY 2009 04:33:37 PM): ; c:\home\.slime\fasl\2009-09-24\sbcl-1.0.29-win32-x86\swank-source-file- cache.fasl written ; compilation finished in 0:00:00.094 ; loading #P"c:\\home\\.slime\\fasl\\2009-09-24\\sbcl-1.0.29-win32-x86\\swank- source-file-cache.fasl" ; compiling file "c:\\home\\bin\\central-registry\\slime\\swank- sbcl.lisp" (written 25 SEP 2009 11:32:52 PM): ; ; compilation unit aborted ; caught 1 fatal ERROR condition ; compilation aborted after 0:00:00.094 ;; ;; Error while loading: c:\home\.slime\fasl\2009-09-24\sbcl-1.0.29-win32- x86\swank-sbcl.fasl ;; Condition: Don't know how to REQUIRE SB-BSD-SOCKETS. ;; See also: ;; The SBCL Manual, Variable *MODULE-PROVIDER-FUNCTIONS* ;; The SBCL Manual, Function REQUIRE ;; Aborting.

3 3

[slime-devel] slime-indentation breaks indentation
by Stanislaw Halik 30 Sep '09

30 Sep '09

I have a macro with such lambda-list: (defmacro fluid-let (&environment env (&rest bindings) &body body) ...) With „slime-indentation”, it gets indented pretty badly: (fluid-let () 42) Without it, it's (correctly) indented as with LET bodies. -- polscy Lispnicy, łączmy się -- #lisp-pl na freenode Lisp stuff: <http://tehran.lain.pl>

1 0

[slime-devel] copious output makes point jump around
by Stanislaw Halik 29 Sep '09

29 Sep '09

Sometimes, not very deterministically, after (require 'foo), point jumps from the prompt way up, into a seemingly random place in copious output. It's not a compilation note, not a warning, but something like "compiling (defun foo ...". It happens even if no notes are emitted. Someone on #lisp confirmed that as well. I don't have any idea on how to debug or isolate it. -- polscy Lispnicy, łączmy się -- #lisp-pl na freenode Lisp stuff: <http://tehran.lain.pl>

1 0

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

29 Sep '09

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1866 slime/ChangeLog:1.1868 --- slime/ChangeLog:1.1866 Sat Sep 26 19:24:50 2009 +++ slime/ChangeLog Mon Sep 28 10:56:19 2009 @@ -1,3 +1,11 @@ +2009-09-28 Stas Boukarev <stassats(a)gmail.com> + + * swank.lisp (set-package): Provide a more meaningful error + message when package doesn't exist. + + * swank-lispworks.lisp (replace-strings-with-symbols): Didn't work on + non-proper lists. Reported by Madhu. + 2009-09-27 Tobias C. Rittweiler <tcr(a)freebits.de> * swank-sbcl.lisp (call-with-debugger-hook): Correctly deal with Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.248 slime/contrib/ChangeLog:1.250 --- slime/contrib/ChangeLog:1.248 Fri Sep 25 02:43:33 2009 +++ slime/contrib/ChangeLog Mon Sep 28 23:21:30 2009 @@ -1,3 +1,13 @@ +2009-09-29 Stas Boukarev <stassats(a)gmail.com> + + * slime-repl.el (slime-sync-package-and-default-directory): + Better checking for packages. + +2009-09-28 Stas Boukarev <stassats(a)gmail.com> + + * slime-repl.el (slime-sync-package-and-default-directory): + Do not try to set package if it doesn't exists. + 2009-09-25 Tobias C. Rittweiler <tcr(a)freebits.de> * swank-sbcl-exts.lisp: Add EVAL-WHEN to prevent subtle dependency

1 0

[slime-devel] buffer readtables
by Tobias C. Rittweiler 28 Sep '09

28 Sep '09

I want to introduce the concept of buffer-readtables so C-c C-c and other commands will be able to process source strings with the right readtable being active. For that, the :EMACS-REX event has to be adapted. At the moment, it looks as follows (:emacs-rex rpc-sexp buffer-package buffer-thread cont-id) My plan is to change it to (:emacs-rex rpc-sexp cont-id buffer-context) where buffer-context is a plist of form (&key buffer-package buffer-thread &allow-other-keys) so that a contrib can extend what constitutes a buffer-context. Are you ok with this? Or is it too general? Should I instead add just another parameter specifically for buffer-readtables? -T.

3 5

[slime-devel] bug: slime-buffer-package not set on connection
by Jeffrey Chu 27 Sep '09

27 Sep '09

Hi, It looks like in slime-buffer-package is not being set after connection and (swank:create-repl nil) is called / returned. This causes things that call (slime-current-package), like slime-c-p-c, to be a little sad when the REPL's default package isn't "COMMON-LISP-USER". >From what I can tell, a good place to apply it is at the end of the slime-repl-connected-hook-function: diff a/contrib/slime-repl.el b/contrib/slime-repl.el --- a/contrib/slime-repl.el +++ b/contrib/slime-repl.el @@ -1519,9 +1519,11 @@ expansion will be added to the REPL's history.)" (let ((slime-current-thread t)) (slime-eval '(swank:create-repl nil))) (setf (slime-lisp-package) package) - (setf (slime-lisp-package-prompt-string) prompt)) - (slime-hide-inferior-lisp-buffer) - (slime-init-output-buffer (slime-connection))) + (setf (slime-lisp-package-prompt-string) prompt) + (slime-hide-inferior-lisp-buffer) + (slime-init-output-buffer (slime-connection)) + (with-current-buffer (slime-output-buffer) + (setf slime-buffer-package package)))) Please let me know if you need any additional information, - Jeff

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel September 2009