- slime-devel - mailman3.common-lisp.net

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

09 Oct '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.962 slime/ChangeLog:1.963 --- slime/ChangeLog:1.962 Tue Oct 3 17:49:29 2006 +++ slime/ChangeLog Sun Oct 8 08:47:50 2006 @@ -1,3 +1,8 @@ +2006-10-08 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> + + * swank-loader.lisp (lisp-version-string) [allegro]: Distinguish + between 32-bit and 64-bit version on the SPARC architecture. + 2006-10-03 Marco Baringer <mb(a)bese.it> Change license statement to say that all files without an explicit

1 0

[slime-devel] setting up *completely* self-contained USB lisp-in-a-box
by John Stoneham 08 Oct '06

08 Oct '06

As the subject indicates, I'm trying to configure a completely self-contained clisp/emacs/slime "lisp box" on a USB thumb drive for lunch-time hacking on a Windows workstation with limited privileges. I'm almost there. If I set HOME to the drive letter of the USB stick before launching emacs, the ".emacs.d" and ".slime" directories are created/used on the USB stick instead of the hard drive. I have a batch file located in the root directory of the thumb drive, and it executes "set HOME=%CD%" before luanching emacs. Seems to do the trick for these directories. However, I've got 2 issues with slime. One is the firewall. When slime starts, I get a Windows Firewall warning that "lisp.exe" is blocked and that only the Administrator can unblock it. However, closing out of the dialog doesn't really have any negative effect that I can tell, and slime seems to be connected to the lisp process and the REPL seems to work as it should. Is there anything I'm missing here? The other issue with this setup is that slime tries to create a temporary file on the hard drive (possibly something to do with the locking the lisp process PID number?), even though HOME points to the thumb drive. Is slime using some other environment variable besides HOME for the location of creating this file? Slime issues a warning about being unable to lock the file or something (I can't recall the exact warning right now). As I said, these machines have fairly limited privileges, which is why I want everything contained on the USB thumb drive, including all temporary files. Any pointers on these 2 issues (or anything else I'm overlooking in setting this up) would be appreciated! Thanks, John

1 0

[slime-devel] when did definterface / defimplementation start making defuns instead of defmethods and why
by Gary King 06 Oct '06

06 Oct '06

Maybe that's too long a subject but it does say it all. When did definterface / defimplementation start making defuns instead of defmethods and why? thanks, -- Gary Warren King, metabang.com Cell: (413) 885 9127 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM

2 1

[slime-devel] Lisp connection closed unexpectedly: exited abnormally with code 256 (with SBCL 0.9.8, elephant)
by Red Daly 06 Oct '06

06 Oct '06

I receive the following error when working a piece of software called Elephant. The following two lines cause my Lisp connection to exit abnormally: (asdf:operate 'asdf:load-op :elephant) (let ((store-spec '(:BDB "store"))) (elephant:open-store store-spec)) The only visible error is a status message in emacs: Lisp connection closed unexpectedly: exited abnormally with code 256 I am running SBCL 0.9.8 on ubuntu dapper 2.6.15-27-386. I do not know what version of slime I have, but I downloaded it within the past few weeks from the slime site. I read about a similar problem that was resolved by using an inferor-lisp-program of "nohup sbcl", but that causes other problems for me (I can elaborate if this seems like the right idea). I am simultaneously involved in a discussion on the elephant-devel mailing list about this same issue. See that thread here: http://common-lisp.net/pipermail/elephant-devel/2006-October/000549.html thanks for any help, red daly

3 2

[slime-devel] Connection to Emacs lost under LispWorks 5.0
by Chris Dean 05 Oct '06

05 Oct '06

When I evaluate (code-char 8217) in the SLIME repl, the Emacs connection to the Lisp process is lost. It looks like lisp is still running when I look at my ps output. This is under Linux using LispWorks 5.0 and the latest CVS slime. The *inferior-lisp* buffer has the message ;; swank:close-connection: #\U+2019 is not of type BASE-CHAR. I assume this is some sort of encoding problem, but I'm not sure where. Any ideas as to how to fix this? Cheers, Chris Dean

1 1

Re: [slime-devel] Re: COPYRIGHT change - slime contributors please read this
by bojohan+lisp＠dd.chalmers.se 05 Oct '06

05 Oct '06

Luca Capello <luca(a)pca.it> writes: >> swank-ecl.lisp (juan jose garcia is ok with putting this file into >> the public domain) > > As from [1], I think we need Johan Bockgård's agreement as well. OK. -- Johan Bockgård

1 0

Re: [slime-devel] Re: COPYRIGHT change - slime contributors please read this
by Espen Wiborg 05 Oct '06

05 Oct '06

Luca Capello <luca(a)pca.it> writes: >> PROBLEMS > > Created by Luke, modified by Helmut, Espen Wiborg and Christophe > Rhodes. My contributions to this file are placed in the public domain. -- Espen Wiborg <ewiborg(a)common-lisp.net> "Dreamt" is the only English word that ends in the letters "mt."

1 0

Re: [slime-devel] Re: COPYRIGHT change - slime contributors please read this
by Douglas Crosher 04 Oct '06

04 Oct '06

Luca Capello wrote: > Hello! > > I'm cc:ing all the interested people (please read below), sorry if > someone of them daily reads SLIME-devel. Please reply to the > SLIME-devel mailing list only (I set R-T and M-F-T accordingly). > > Peter, I cc:ing you FYI, as you're the Debian SLIME maintainer. > > On Wed, 04 Oct 2006 01:33:07 +0200, Marco Baringer wrote: >> what i really meant to say here was: what should I do for those files >> which have no copyright notice in them? >> >> The files in question are: >> >> swank-ecl.lisp (juan jose garcia is ok with putting this file into >> the public domain) > > As from [1], I think we need Johan Bockgård's agreement as well. > Moreover, the file was modified by Helmut Heller and Douglas Crosher. > I think we also need to add the copyright statement (or at least a > note about its authors). All of my contributions to SLIME are placed in the Public Domain. Regards Douglas Crosher

1 0

Re: [slime-devel] Re: COPYRIGHT change - slime contributors please read this
by Luca Capello 04 Oct '06

04 Oct '06

Hello again! On Thu, 05 Oct 2006 00:48:04 +0200, Luca Capello wrote: > On Wed, 04 Oct 2006 01:33:07 +0200, Marco Baringer wrote: >> what i really meant to say here was: what should I do for those files >> which have no copyright notice in them? >> >> The files in question are: I forgot the ChangeLog file: as Peter Van Eynde stated on the debian/copyright file, this is a generated file and probably it can be considered a derivative of the others. FWIW, its first author was Luke Gorrie :-) Thx, bye, Gismo / Luca

1 0

[slime-devel] COPYRIGHT change - slime contributors please read this
by Marco Baringer 04 Oct '06

04 Oct '06

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

4 3