slime-devel October 2011

slime-devel@common-lisp.net

19 participants
20 discussions

[slime-devel] Question about Slime & SBCL on Windows
by Scott Turner 29 Nov '11

29 Nov '11

I'm currently using SLIME & SBCL (SBCL 1.0.50.24.mswinmt.876-cad5ed2 -- Kovalenko's Windows port). When I hit C-c C-c to interrupt, my Lisp dies and I have to kill Slime and restart. Am I doing something wrong, or is interrupt just not supported on SBCL? Thanks in advance for any help! -- Scott Turner

3 7

[slime-devel] Slime and clusters
by Zach Kost-Smith 31 Oct '11

31 Oct '11

I wonder if anybody has yet to tread this path. I have been using CL at on my school's cluster. I usually develop within Slime locally, then move it to the cluster's master node and have a trial run over a remote Slime session, then once everything works, I ditch Slime and invoke my programs on the worker nodes using a bash or Lisp script (yes, we are running without a queue; crazy, huh?). I would very much like to use dispatch the jobs to the worker nodes from within Slime. More to the point, I would like to be able to start jobs on the worker nodes from my Slime connection to the master node. Now, of course I can connect to each node using a tunnel and start the jobs that way, but I want an automated interface as sketched below. I was thinking about developing something that would work for me and perhaps others. I just wanted to put this out there first to make sure it hasn't already been done and see if there are any suggests or comments on an undertaking like this. Basically all I would do is define a CL client for swank and use that to connect to worker Lisps running on each worker node from the one instance on the master. Then, if I want to send a job to the first node, all I have to do is send some code over the swank connection for the worker to evaluate and return the value. I also thought I'd write a kind of forwarder for the Swank connection so I can jump to a worker node from the master by setting the master to forward all data to the worker, and return anything coming from the worker down its connect to Slime (although, I suppose this could be arbitrarily deep, this is analogous to jumping from server to server using ssh but without the secure-ness). I am fairly convinced that this will also work (sans persistent worker Lisps) for any cluster with a queuing system that allows for interactive jobs (like the Torque/Moab combo that we use on another cluster here) and probably in a EC2 Cloud like environment as well. I'm just saying that it is possible that this could be generally useful for other people as well. Almost all of this would be on the Swank side (and thank goodness because I feel like a fish out of water in ELisp). However, I have already had trouble understanding the Slime message protocol. I'll figure it out eventually, but are there any good internals guides for Slime/Swank? Any advice is appreciated, Zach KS

3 2

[slime-devel] Unicode character misbehavior?
by Jeffrey Cunningham 30 Oct '11

30 Oct '11

I discovered a way to crash Slime by compiling a simple sexp containing a string. Here are the conditions: 1. Connect to a running SBCL via swank (M-x slime-connect). 2. Cut and paste the sexp below containing the smiley-face into a lisp file. 3. Compile the fragment. That's it. When I do this the inferior Lisp process is terminated "by remote peer". (let ((dangerous-string "This is a smiley-face: ☺")) (print "Important safety tip: don't do this.")) I normally only work with UTF-8 characters, and my ignorance of handling other character sets is probably the culprit here. What should I do if I want to enable slime to work with strings like this? Regards, Jeff Cunningham

9 15

[slime-devel] Daily ChangeLog diff
by Helmut Eller 30 Oct '11

30 Oct '11

Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.499 slime/contrib/ChangeLog:1.500 --- slime/contrib/ChangeLog:1.499 Fri Oct 7 05:50:20 2011 +++ slime/contrib/ChangeLog Sat Oct 29 04:15:15 2011 @@ -1,3 +1,14 @@ +2011-10-29 Nikodemus Siivola <nikodemus(a)random-state.net> + + Two patches by Tomohiro Matsuyama <tomo(a)cx4a.org>. + + * slime-cl-indent.el (define-common-lisp-style): Fix handling + of :documentation option, which accidentally threw out the docstring. + (lisp-indent-lambda-list-keywords-regexp): Handle trailing + &allow-other-keys correctly. + + * slime-cl-indent-test.txt: Tests 50-53. + 2011-10-07 Stas Boukarev <stassats(a)gmail.com> * slime-repl.el (slime-repl-clear-output): Fix clearing output

1 0

[slime-devel] Error: Searching for program: no such file or directory, sbcl
by ishi soichi 29 Oct '11

29 Oct '11

my environment: MacOSX SnowLeopard Cocoa Emacs 23.2 SBCL 1.0.51.0-a546163 Slime latest (I think...) The installation of sbcl is fine. I can launch sbcl in terminal. But when launching slime in Emacs, it give an error Searching for program: no such file or directory, sbcl Can anyone tell my what's wrong with my setting? in .emacs file, I have written the following. ;;------------- (setq inferior-lisp-program "/usr/local/bin/sbcl --noinform") (setq slime-lisp-implementations '((sbcl ("sbcl") :coding-system utf-8-unix) (cmucl ("cmucl") :coding-system iso-latin-1-unix))) (add-to-list 'load-path "~/.emacs.d/slime") (add-hook 'lisp-mode-hook (lambda () (slime-mode t) (show-paren-mode))) (require 'slime) (slime-setup) ;;----------- Thanks in advance, soichi

2 2

[slime-devel] define-common-lisp-style bug and fix
by Tomohiro Matsuyama 29 Oct '11

29 Oct '11

An option passing to documentation argument of define-common-lisp-style is ignored. I attached the patch. Please check it out. Tomohiro

2 1

[slime-devel] slime-cl-indent.el: Invalid lambda-list-regexp
by Tomohiro Matsuyama 29 Oct '11

29 Oct '11

Indenting &allow-other-keys in lambda-list is invalid. Please check out attached patch. Tomohiro

2 1

[slime-devel] meta-. off by several lines on SLIME/ACL/Emacs/Windows, anyone seen this?
by mhd＠yv.org 28 Oct '11

28 Oct '11

When I do meta-., it takes me there, but it's off by several lines, and at a random place in the middle of the line. I think it's consistently above the def. But not by the same amount of lines each time. And I'm in a random part of the line. Should be at the beginning, right? It's stable in a session: two repeated meta-.'s take me to the same place each time. Admittedly, I've not any home work on versions of SLIME/Emacs/ACL/Windows. Not asking for anyone to do any more than say if they recall anything like this. I use SBCL and CCL with the otherwise-same stack with no similar problems

5 6

[slime-devel] Feature suggestion + minor inspector bug
by Max Mikhanosha 22 Oct '11

22 Oct '11

It would be really cool if XREF invoked by slime-edit-definition key, would have a key binding and a button to remove a method similar to fancy inspector. It feels silly to go back to REPL and type #'generic-function and inspect it to remove the method. The inspector bug is that 1st time you invoke inspector, is that "g" key in the inspector is not using the same readtable as original invocation of inspector. I'm using inverted readtable, and (named-readtables:in-readtable :my-readtable) in the file.lisp. Somehow when I'm inspecting objects printed in REPL, they are printed in the inspector in lower case, picking up the inverted readtable from the buffer somehow. But pressing "g" key refreshes everything in the upper case, going back to default readdable. It seems I can fix this by doing (in-readtable) in the REPL, and then it always use the inverted one. Imho principle of least surprise requires that pressing "g" key to refresh inspector view, that it would use the same readtable that view was generated with.

2 1

[slime-devel] Daily ChangeLog diff
by Helmut Eller 20 Oct '11

20 Oct '11

Index: slime/ChangeLog diff -u slime/ChangeLog:1.2219 slime/ChangeLog:1.2220 --- slime/ChangeLog:1.2219 Thu Oct 13 02:24:02 2011 +++ slime/ChangeLog Wed Oct 19 02:47:57 2011 @@ -1,3 +1,8 @@ +2011-10-19 Andrew Myers <asm198(a)gmail.com> + + * swank-allegro.lisp (frob-allegro-field-def): Add missing type to + ecase for inspector. + 2011-10-13 Helmut Eller <heller(a)common-lisp.net> * swank.lisp (all-completions): Remove mixed case syms e.g |Foo|.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel October 2011