So I'm lagging behind my original plan vis a vis the Practical Common Lisp Lispbox distribution. (I've got preliminary versions of OS X and GNU/Linux Lispboxes up.) So now that it's mid-April is there any chance of an official 1.1 release of SLIME. To date I've been making my own "releases" out of CVS HEAD but it'd be nice to have an official one.
-Peter
Peter Seibel peter@gigamonkeys.com writes:
So I'm lagging behind my original plan vis a vis the Practical Common Lisp Lispbox distribution. (I've got preliminary versions of OS X and GNU/Linux Lispboxes up.) So now that it's mid-April is there any chance of an official 1.1 release of SLIME. To date I've been making my own "releases" out of CVS HEAD but it'd be nice to have an official one.
If tagged the release with SLIME-1-2. A tarball can be found at
http://common-lisp.net/project/slime/slime-1.2.tgz
but it isn't yet linked from web page. I also uploaded a html version of the manual at:
http://common-lisp.net/project/slime/html-doc/slime.html
So, what's missing is the updated web page and maybe an announcement in comp.lang.lisp.
Helmut.
Helmut Eller heller@common-lisp.net writes:
Peter Seibel peter@gigamonkeys.com writes:
So I'm lagging behind my original plan vis a vis the Practical Common Lisp Lispbox distribution. (I've got preliminary versions of OS X and GNU/Linux Lispboxes up.) So now that it's mid-April is there any chance of an official 1.1 release of SLIME. To date I've been making my own "releases" out of CVS HEAD but it'd be nice to have an official one.
If tagged the release with SLIME-1-2. A tarball can be found at
Is that a tarball of the whole tree or a distribution made with mkdist.sh? That is, I realize, a nitpicky question, but I wonder because mkdist.sh usually makes a tar.gz rather than a .tgz file. Which matters to me because my Lispbox build process needs to know how to unpack and build the various components that make up Lispbox. Also I'm anal enough to worry about whether distributions are being built in a consistent way, i.e. preferably with mkdist.sh.
-Peter
Peter Seibel peter@gigamonkeys.com writes:
Is that a tarball of the whole tree or a distribution made with mkdist.sh?
Yes, it was created with mkdist, but the tarball is now obsolete anyway.
Helmut.
Helmut Eller heller@common-lisp.net writes:
Peter Seibel peter@gigamonkeys.com writes:
Is that a tarball of the whole tree or a distribution made with mkdist.sh?
Yes, it was created with mkdist, but the tarball is now obsolete anyway.
Ah, so that's not the official 1.2 release? I included it in the 0.3 Lispboxen. I assume you'll anounce here when there's an official 1.2 I can use. I'll build Lispbox 0.4 when it's ready (or after I get back from Amsterdam). And, just out of curiosity, how is it that it ended up named .tgz instead of tar.gz if it was built with mkdist? Did you just rename it?
-Peter
Peter Seibel peter@gigamonkeys.com writes:
Ah, so that's not the official 1.2 release?
Well, we decided to include the fix for SBCL threading issue and move the tag. See the other thread.
I included it in the 0.3 Lispboxen. I assume you'll anounce here when there's an official 1.2 I can use. I'll build Lispbox 0.4 when it's ready (or after I get back from Amsterdam). And, just out of curiosity, how is it that it ended up named .tgz instead of tar.gz if it was built with mkdist? Did you just rename it?
Yeah, to much typing like scp slime-1.2.tar.gz heller@common-lisp.net:/project/slime/public_html/slime-1.2.tgz
Helmut.
Helmut Eller heller@common-lisp.net writes:
Yeah, to much typing like scp slime-1.2.tar.gz heller@common-lisp.net:/project/slime/public_html/slime-1.2.tgz
Shouldn't scp slime-1.2.tar.gz heller@common-lisp.net:/project/slime/public_html/ also work? ;)
Kind regards,
Dirk Gerrits
Helmut Eller heller@common-lisp.net writes:
Peter Seibel peter@gigamonkeys.com writes:
Ah, so that's not the official 1.2 release?
Well, we decided to include the fix for SBCL threading issue and move the tag. See the other thread.
So I see there's now a slime-1.2.tar.gz on common-lisp.net. Is that the official release?
-Peter
Peter Seibel peter@gigamonkeys.com writes:
So I see there's now a slime-1.2.tar.gz on common-lisp.net. Is that the official release?
That was a temporary link to the .tgz file.
I replaced it now with new (hopefully) official release.
Helmut.
I just commited a change to bind *PRINT-ESCAPE* to NIL in arglist display. This is the difference between
(with-open-file (var &rest lisp::open-args) &parse-body (forms lisp::decls)) and the nicer (with-open-file (var &rest open-args) &parse-body (forms decls))
Did I miss something, or is this something that should go in the release?
I had forgotten how lame releasing things is :-)
On 20 Apr 2005 19:30:25 +0200, Luke Gorrie luke@synap.se said:
Luke> I just commited a change to bind *PRINT-ESCAPE* to NIL in arglist Luke> display. This is the difference between
Luke> (with-open-file (var &rest lisp::open-args) &parse-body (forms lisp::decls)) Luke> and the nicer Luke> (with-open-file (var &rest open-args) &parse-body (forms decls))
Luke> Did I miss something, or is this something that should go in the release?
Keywords maybe? E.g.
(defmacro confusion (&key ((:the-keyword the-variable))) `(list ,the-variable))
__Martin
Martin Simmons martin@lispworks.com writes:
Luke> Did I miss something, or is this something that should go in the release?
Keywords maybe? E.g.
(defmacro confusion (&key ((:the-keyword the-variable))) `(list ,the-variable))
Also default values: (defun foo (&optional (a "a")) ...)
Helmut.
Helmut Eller heller@common-lisp.net writes:
Martin Simmons martin@lispworks.com writes:
Luke> Did I miss something, or is this something that should go in the release?
Keywords maybe? E.g.
(defmacro confusion (&key ((:the-keyword the-variable))) `(list ,the-variable))
Also default values: (defun foo (&optional (a "a")) ...)
Darn, it really messes with strings. I would like to strip the package names of parameter names but it seems a more sophisticated approach would be needed. I have rolled back the change.