slime-devel

slime-devel@common-lisp.net

4231 discussions

[slime-devel] Recursive errors
by Dan Weinreb 04 Oct '06

04 Oct '06

Try doing the following in a Slime REPL buffer, in SBCL: Type (/ 1 0), entering SLDB Type E, get prompted for a form to eval Type (aref nil 0), entering a recursive SLDB Type 0, to return to the outer SLDB. Fails: Swank tries to evaluate *sldb-stack-top* but it is unbound. -- Dan

1 0

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 03 Oct '06

03 Oct '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.961 slime/ChangeLog:1.962 --- slime/ChangeLog:1.961 Mon Oct 2 11:29:02 2006 +++ slime/ChangeLog Tue Oct 3 17:49:29 2006 @@ -1,3 +1,11 @@ +2006-10-03 Marco Baringer <mb(a)bese.it> + + Change license statement to say that all files without an explicit + copyright notice are public domain. This change will allow SLIME + to moved out of debian's nonfree tree. + + * README: Update license statement. + 2006-10-02 Marco Baringer <mb(a)bese.it> * slime.el (slime-highlight-compiler-notes): New variable.

1 0

RE: [slime-devel] COPYRIGHT change - slime contributors please read this
by Bradford W Miller 03 Oct '06

03 Oct '06

I don't think this is a good idea for two reasons. 1) you don't have the right to put anything but your own work into the public domain (and even then because of implicit copyrights, etc. even a dedication to the public domain may not be sufficient). 2) by putting the work into the public domain you lose all control over it - someone else can sell it, and take credit for it for instance, and the author (or anyone else for that matter) will have no recourse. For some information on how to put something in the public domain, see: http://www.fin.ucar.edu/legal/faq_publicdomain.html I don't want to discourage you from putting your work into the public domain (assuming it is possible), but rather note that your statement that something is in the public domain carries no weight if it is not owned by you in the first place. Copyright, is in fact implicit when a work is fixed (i.e. written to disk), so it is held by the author (or in the case of a work for hire, by the client) regardless of having an explicit notice. If you want to put something into the public domain, you will at the very least have to have the author submit a statement of dedication to that effect. Brad Miller -----Original Message----- From: slime-devel-bounces(a)common-lisp.net [mailto:slime-devel-bounces@common-lisp.net] On Behalf Of mb(a)bese.it Sent: Tuesday, October 03, 2006 5:54 PM To: slime-devel(a)common-lisp.net Subject: [slime-devel] COPYRIGHT change - slime contributors please read this hi, I have changed the license statement in SLIME's README. it used to be: ------------------------------------------------------------------------ SLIME is free software. The source files are licensed separately for maximum compatibility with their host environment, for example slime.el is GPL and swank-cmucl.lisp is public domain. See the source files for more details. ------------------------------------------------------------------------ It is now this: ------------------------------------------------------------------------ SLIME is free software. All files, unless explicitly stated otherwise, are public domain. ------------------------------------------------------------------------ So if you've contributed code to SLIME and haven't supplied a copyright statement your code is now public domain. If you have an issue with this please bring it up asap. For what it's worth the only files which were missing a copyright statement were swank-ecl.lisp, doc/Makefile, HACKING, NEWS, PROBLEMS and README. juan jose garcia (the original author of swank-ecl.lisp) is ok with the change so I don't think anyone should be surprised be this change. -- -Marco Ring the bells that still can ring. Forget your perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen _______________________________________________ slime-devel site list slime-devel(a)common-lisp.net http://common-lisp.net/mailman/listinfo/slime-devel

2 2

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 02 Oct '06

02 Oct '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.960 slime/ChangeLog:1.961 --- slime/ChangeLog:1.960 Wed Sep 27 18:53:45 2006 +++ slime/ChangeLog Mon Oct 2 11:29:02 2006 @@ -1,3 +1,9 @@ +2006-10-02 Marco Baringer <mb(a)bese.it> + + * slime.el (slime-highlight-compiler-notes): New variable. + (slime-compilation-finished): Only highlight notes when + slime-highlight-compiler-notes is non-NIL. + 2006-09-28 Marco Baringer <mb(a)bese.it> * swank-loader.lisp (compile-files-if-needed-serially): Don't

1 0

[slime-devel] Sldb closes connection with Clisp restarts?
by Gregory Novak 01 Oct '06

01 Oct '06

If I type (undefined-function) at the slime repl, I get the (expected) sldb backtrace with possible restarts. If I choose any of them (except "Abort Slime Request") slime closes the connection. I've tried this on a variety of different Emacs, Slime versions, and Clisp versions including: Emacs: 21.3, 21.4, cvs from 5-17-06 Slime: cvs from 1-20-06 and ~1 hour ago Clisp: 2.35, 2.39 OS: OS X and some version of FreeBSD Notably this doesn't happen when I use Sbcl instead of Clisp. That is, I can still type at the Repl after exiting the slime debugger with Sbcl. Thanks! Greg

1 0

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 27 Sep '06

27 Sep '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.958 slime/ChangeLog:1.960 --- slime/ChangeLog:1.958 Sun Sep 24 17:52:55 2006 +++ slime/ChangeLog Wed Sep 27 18:53:45 2006 @@ -1,3 +1,13 @@ +2006-09-28 Marco Baringer <mb(a)bese.it> + + * swank-loader.lisp (compile-files-if-needed-serially): Don't + ignore compile-time errors but drop into a debugger (it's not a + slime debugger but it's certainly better than ignoring the error). + +2006-09-27 Marco Baringer <mb(a)bese.it> + + * swank.lisp (*globally-redirect-io*): Change default value to T. + 2006-09-25 Juho Snellman <jsnell(a)iki.fi> Fix Slime on SBCL 0.9.17.

1 0

[slime-devel] why does swank:*globally-redirect-io* defalut to NIL?
by Marco Baringer 27 Sep '06

27 Sep '06

i'd imagine that, for most development setup and for newbies, getting output setup to *inferior-lisp* or the remote slime's terminal is not what you want. any problems if i change this to t? -- -Marco Ring the bells that still can ring. Forget your perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen

4 4

[slime-devel] inspecting network streams on sbcl
by Attila Lendvai 27 Sep '06

27 Sep '06

hi! when a network stream is inspected on sbcl then i get this error: The value NIL is not of type PATHNAME. [Condition of type TYPE-ERROR] Restarts: 0: [ABORT] Return to sldb level 1. 1: [CONTINUE] Return from BREAK. 2: [TERMINATE-THREAD] Terminate this thread (#<THREAD "an httpd worker 21" {C7D69F9}>) Backtrace: 0: (PATHNAME #<SB-SYS:FD-STREAM for "a constant string" {D53DE31}>) 1: ((SB-PCL::FAST-METHOD SWANK-BACKEND:INSPECT-FOR-EMACS (STREAM-ERROR T)) #<unavailable argument> #S(SB-PCL::FAST-METHOD-CALL :FUNCTION #<FUNCTION (SB-PCL::FAST-METHOD SWANK-BACKEND:INSPECT-FOR-EMACS #)> :PV-CELL NIL :NEXT-METHOD-CALL #S(SB-PCL::FAST-METHOD-CALL :FUNCTION #<FUNCTION #> :PV-CELL NIL :NEXT-METHOD-CALL NIL :ARG-INFO (2)) :ARG-INFO (2)) #<SB-INT:SIMPLE-STREAM-ERROR {D53C4D1}> #<SWANK-BACKEND::SBCL-INSPECTOR {C6C7A99}>) 2: (SWANK::INSPECT-OBJECT #<SB-INT:SIMPLE-STREAM-ERROR {D53C4D1}> #<SWANK-BACKEND::SBCL-INSPECTOR {C6C7A99}>) 3: ((SB-PCL::FAST-METHOD SWANK-BACKEND:CALL-WITH-SYNTAX-HOOKS (T)) #<unused argument> #<unused argument> #<CLOSURE (LAMBDA NIL) {C6C7865}>) looking at swank.lisp it does check for (typep stream 'file-stream) but it is T for socket streams which probably is the root of the problem. also note the strange printed representation of the socket stream, but i guess it's also an sbcl thing. maybe i should have written this to sbcl-devel... hth, -- - attila "- The truth is that I've been too considerate, and so became unintentionally cruel... - I understand. - No, you don't understand! We don't speak the same language!" (Ingmar Bergman - Smultronstället)

2 1

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 24 Sep '06

24 Sep '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.957 slime/ChangeLog:1.958 --- slime/ChangeLog:1.957 Thu Sep 21 13:36:18 2006 +++ slime/ChangeLog Sun Sep 24 17:52:55 2006 @@ -1,3 +1,18 @@ +2006-09-25 Juho Snellman <jsnell(a)iki.fi> + + Fix Slime on SBCL 0.9.17. + + * swank-backend.lisp (ignored-xref-function-names): New interface + + * swank.lisp (sanitize-xrefs): Use ignored-xref-function-names + instead of having a #+sbcl special case. + + * swank-sbcl.lisp (ignored-xref-function-names): Implement. + Filter out SB-C::STEP-VALUES, not just SB-C::STEP-FORM, as done by + the old sanitize-xrefs. Don't implement the interface at all if + SBCL is sufficiently new (those symbols don't exist any more, and + there's nothing in their place to be ignored). + 2006-09-21 Marco Baringer <mb(a)bese.it> * swank.lisp (find-definitions-for-emacs): Don't return locations

1 0

[slime-devel] REPL-to-regression-test made easy.
by Vladimir Sedach 24 Sep '06

24 Sep '06

Hello everybody, At Friday's inaugural Calgary Lisp user group meeting, Michael Beauregard suggested a feature to SLIME that would let you take an expression-result pair from REPL interaction and easily add it as a new regression test to a test suite. Here is some code that does something like that: (defvar *slime-last-repl-input*) (defvar *slime-last-repl-result*) (defvar *slime-last-repl-input-matches-last-result* nil) ;; set to T if last input expression returned normally and it is safe to save the input-result pair as a unit test, nil otherwise (defvar *slime-regression-test-file* nil "Pathname of file containing test cases to which the next test case will be appended to.") (defvar *slime-regression-test-framework* nil "The unit test framework should be a function that takes as arguments the input and expected result of the unit test as strings and produces an object that is suitable to be serialized and appended to a file containing unit tests for that particular framework.") (defun slime-MIT-regression-testing-framework (input result) (princ "(deftest " (current-buffer)) (princ (gensym) (current-buffer)) (newline) (princ "(multiple-value-list " (current-buffer)) (princ input (current-buffer)) (princ ")" (current-buffer)) (newline) (princ result (current-buffer)) (princ ")" (current-buffer))) (defun slime-save-last-input-as-regression-test () "When called, takes the last REPL expression sent to Lisp by SLIME and the output it returns, and adds them as a unit test to the unit test file specified by *slime-regression-test-file*. If the last REPL command resulted in an error, does nothing. The specific brand of regression testing framework you're using is controlled by *slime-regression-test-framework*." (interactive) (unless *slime-regression-test-file* (call-interactively #'slime-set-regression-test-file)) (when *slime-last-repl-input-matches-last-result* (with-temp-buffer (lisp-mode) (newline) (let* ((res *slime-last-repl-result*) (results (cons 'list (cond ((equal :values (car res)) (second res)) ((equal :present (car res)) (mapcar #'car (second res))) (t "nil"))))) (funcall *slime-regression-test-framework* *slime-last-repl-input* results)) (newline) (indent-region (point-min) (point-max) nil) (append-to-file (point-min) (point-max) *slime-regression-test-file*)))) (defun slime-set-regression-test-file (file) (interactive "FRegression test file: ") (setf *slime-regression-test-file* file)) (defadvice slime-repl-eval-string (before regression-testing-string-capturer (string)) "Get the string passed to slime-repl-eval-string before it gets mangled." (setf *slime-last-repl-input* (copy-seq string))) ;;; need to redefine slime-repl-eval-string (defun slime-repl-eval-string (string) (slime-rex () ((list 'swank:listener-eval string) (slime-lisp-package)) ((:ok result) ;;; modified code be here (setf *slime-last-repl-result* result *slime-last-repl-input-matches-last-result* t) ;;; end modified code (with-current-buffer (slime-output-buffer) (slime-repl-insert-prompt result))) ((:abort) ;;; modified code be here (setf *slime-last-repl-input-matches-last-result* nil) ;;; end modified code (slime-repl-show-abort)))) Comments? I don't use regression testing tools very much myself, so the first thing I want to ask, is this approach going to work for the commonly used CL testing frameworks, or is something more flexible necessary? If this were to become part of SLIME, the big question is, what key should slime-save-last-input-as-regression-test be bound to? Having just the last repl-expression-result pair is probably good enough, but is there anyone wanting a history of expression-result pair interactions and a nice colorful-buffer way of choosing which ones to save? Vladimir

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel