slime-devel

slime-devel@common-lisp.net

4231 discussions

[slime-devel] Fwd: datagram socket error on Allegro CL
by Dave Cooper 23 Jan '13

23 Jan '13

Dear Slime list, This error probably falls in between Franz support and appropriate for this list, but maybe someone has seen it so I'll ask here. This is on Allegro CL 9.0 Windows, when trying to initialize the Slime connection: "creating a datagram socket resulted in error: (code 10013): Unknown error. [Condition of type excl:errno-stream-error] This appears to be some kind of permissions problem... has anyone seen it before? -- My Best, Dave Cooper, Genworks Support david.cooper(a)genworks.com, dave.genworks.com(skype) USA: 248-327-3253(o), 1-248-330-2979(mobile)

2 2

[slime-devel] Daily ChangeLog diff
by Helmut Eller 20 Jan '13

20 Jan '13

Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.563 slime/contrib/ChangeLog:1.564 --- slime/contrib/ChangeLog:1.563 Thu Jan 10 03:45:48 2013 +++ slime/contrib/ChangeLog Sat Jan 19 22:37:32 2013 @@ -1,3 +1,13 @@ +2013-01-20 Stas Boukarev <stassats(a)gmail.com> + + * swank-asdf.lisp: Better compatibility with newer ASDF. + Patch by Francois-Rene Rideau and Stelian Ionescu. + + Remove auto-upgrading. + Rename *asdf-directory* to *asdf-path*, to be a full path to + asdf.lisp. + Remove #+gcl and #+genera. + 2013-01-10 Helmut Eller <heller(a)common-lisp.net> * slime-autodoc.el (slime-autodoc): Remove :gnu-emacs-only.

1 0

[slime-devel] Why not adopt asdf?
by Faré 20 Jan '13

20 Jan '13

Could SLIME adopt ASDF as a way to compile itself and other software? I understand that ASDF was quite insufficient for the needs of SLIME back in the bad old days, but these days, ASDF 2 (1) is available via (require "asdf") on *every* implementation that has been released in the last two years (i.e. not on corman gcl genera rmcl scl - though it runs on all of them) (2) already manages a decent FASL cache so SLIME doesn't have to. (3) can upgrade itself correctly if needed. ASDF has also improved a lot in the last few years. The upcoming release 2.27 formalizes a lot of the portability support that had accumulated through the years, improves on it, and adds features like condition control, saving of deferred warnings, image dump and restore, etc. In any case, that would be as much bad code duplication that could die. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org If debugging is the process of removing bugs, then programming must be the process of putting them in. — Dijkstra

4 3

[slime-devel] Some love for swank-asdf.lisp
by Faré 19 Jan '13

19 Jan '13

This makes swank-asdf behave nicer on recent ASDFs. It also kills support for versions of ASDF older than 2.014.6. Quicklisp has used 2.014.6 for a year and a half, and finally upgraded to 2.26; I don't see any reason to support older versions than that. CLISP still ships with 2.011? If they don't upgrade their, you should install an upgraded version in your source registry. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org We don't want tradition. We want to live in the present and the only history that is worth a tinker's dam is the history we make today. — Henry Ford

3 3

[slime-devel] hook around eval-for-emacs
by Anton Vodonosov 16 Jan '13

16 Jan '13

Hello. Could you add a hook around eval-for-emacs, as show in the attached patch? It would allow maintain custom context for all the slime requests. My use case is that I have this tool: https://github.com/avodonosov/local-package-aliases. It allows me to say that in my package $a:plist-alist means alexandria:plist-alist It is portable and in my opinion convenient, but as the aliases are handled by reader macro, slime does not understand tokens like $a:plist-alist, because it can't find package $a. In result slime completion, function arguments hints, go-to-definition doesn't work. The solution I found is that during evaluation of any slime request, if the package designated by swank::*buffer-package* has alias mapping, I temporary add all these aliases as nicknames to the corresponding packages. That's why I need a hook around evaluation of every expression received by swank::eval-for-emacs. With the swank patch applied, I add this hook: (defun swank-eval-for-emacs-hook (next-fn) (local-package-aliases::call-with-nicknames (local-package-aliases::alias-table-for swank::*buffer-package*) next-fn)) (push 'swank-eval-for-emacs-hook swank::*around-eval-for-emacs-hook*) and slime completion, go-to-definition, function parameters hints all start working. Best regards, - Anton

2 1

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

13 Jan '13

Index: slime/ChangeLog diff -u slime/ChangeLog:1.2388 slime/ChangeLog:1.2389 --- slime/ChangeLog:1.2388 Fri Jan 11 15:36:35 2013 +++ slime/ChangeLog Sat Jan 12 04:32:20 2013 @@ -1,3 +1,7 @@ +2013-01-12 Stas Boukarev <stassats(a)gmail.com> + + * swank-backend.lisp: Add a couple of ignore declarations. + 2013-01-11 Stas Boukarev <stassats(a)gmail.com> * swank-ecl.lisp (accept-connection): Fix a typo, line => :line.

1 0

[slime-devel] Daily ChangeLog diff
by Helmut Eller 12 Jan '13

12 Jan '13

Index: slime/ChangeLog diff -u slime/ChangeLog:1.2387 slime/ChangeLog:1.2388 --- slime/ChangeLog:1.2387 Fri Jan 11 01:00:30 2013 +++ slime/ChangeLog Fri Jan 11 15:36:35 2013 @@ -1,3 +1,7 @@ +2013-01-11 Stas Boukarev <stassats(a)gmail.com> + + * swank-ecl.lisp (accept-connection): Fix a typo, line => :line. + 2013-01-11 Helmut Eller <heller(a)common-lisp.net> * swank.lisp (swank-compile-file*): Renamed from

1 0

[slime-devel] Situation where I need (with-compilation-unit () ...) wrapped around both the load and the compile
by Dave Cooper 11 Jan '13

11 Jan '13

Hi All, So I think I have a situation with compiling and loading a file where it needs (with-compilation-unit () (load (compile-file ... ))) in order not to have spurious warnings about undefined functions. If anyone is interested in details I can give as many as you would like, but first I'd just like to ask if, assuming this is a legitimate problem, it makes sense to take care of such a thing by extending swank:compile-file-with-compile-file ? >From studying the sources, it is not entirely clear to me where the actual (load ... ) is taking place, so I am not sure where one would wrap the (with-compilation-unit () ...) even if it turns out that this will be a reasonable thing to do... Has anyone seen something like this or has any ideas? And Happy New Year (the year is still only 10 days old, so still can say that, I guess... :) -- My Best, Dave Cooper, Genworks Support david.cooper(a)genworks.com, dave.genworks.com(skype) USA: 248-327-3253(o), 1-248-330-2979(mobile)

3 2

[slime-devel] Daily ChangeLog diff
by Helmut Eller 11 Jan '13

11 Jan '13

Index: slime/ChangeLog diff -u slime/ChangeLog:1.2385 slime/ChangeLog:1.2387 --- slime/ChangeLog:1.2385 Wed Jan 9 06:29:50 2013 +++ slime/ChangeLog Fri Jan 11 01:00:30 2013 @@ -1,3 +1,12 @@ +2013-01-11 Helmut Eller <heller(a)common-lisp.net> + + * swank.lisp (swank-compile-file*): Renamed from + compile-file-with-compile-file. + +2013-01-10 Helmut Eller <heller(a)common-lisp.net> + + * swank-ecl.lisp (frame-var-value): Return the value without name. + 2013-01-09 Helmut Eller <heller(a)common-lisp.net> * swank.lisp (frame-locals-for-emacs): Print variable names in Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.562 slime/contrib/ChangeLog:1.563 --- slime/contrib/ChangeLog:1.562 Fri Jan 4 10:22:01 2013 +++ slime/contrib/ChangeLog Thu Jan 10 03:45:48 2013 @@ -1,3 +1,9 @@ +2013-01-10 Helmut Eller <heller(a)common-lisp.net> + + * slime-autodoc.el (slime-autodoc): Remove :gnu-emacs-only. + Suggested by Raymond Toy. + (slime-autodoc): Fix long lines. + 2013-01-04 Stas Boukarev <stassats(a)gmail.com> * slime-fancy-inspector.el (slime-edit-inspector-part): New

1 0

[slime-devel] Test Error
by Paul Bowyer 11 Jan '13

11 Jan '13

Hello Helmut: When I run the test, ./test.sh -S emacs sbcl I get one unexpected failure. The following snippet was copied from the test output in the terminal window. -------------------------------------------------------------------------------------------------------- ** input: (swank::compile-file ((swank::compile-file swank::compile-file-for-emacs swank::compile-file-if-needed swank::compile-file-output swank::compile-file-pathname) swank::compile-file)) FAILED: Completion set: expected: [(("swank::compile-file" "swank::compile-file-for-emacs" "swank::compile-file-if-needed" "swank::compile-file-output" "swank::compile-file-pathname") "swank::compile-file")] actual: [(("swank::compile-file" "swank::compile-file-for-emacs" "swank::compile-file-if-needed" "swank::compile-file-output" "swank::compile-file-pathname" "swank::compile-file-with-compile-file") "swank::compile-file")] ERROR: (error "Check failed: \"Completion set: expected: [((\\\"swank::compile-file\\\" \\\"swank::compile-file-for-emacs\\\" \\\"swank::compile-file-if-needed\\\" \\\"swank::compile-file-output\\\" \\\"swank::compile-file-pathname\\\") \\\"swank::compile-file\\\")] actual: [((\\\"swank::compile-file\\\" \\\"swank::compile-file-for-emacs\\\" \\\"swank::compile-file-if-needed\\\" \\\"swank::compile-file-output\\\" \\\"swank::compile-file-pathname\\\" \\\"swank::compile-file-with-compile-file\\\") \\\"swank::compile-file\\\")]\"") -------------------------------------------------------------------------------------------------------- I'm using SBCL-1.1.3 that I compiled from source using SBCL-1.0.58-linux, but the same error comes up if I run the test against SBCL-1.0.58-linux. I like to compile my own so I have the manual handy rather than waiting for the browser. Paul Bowyer

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel