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

[slime-devel] Small fix for swank-lispworks
by Antonio Menezes Leitao 04 Feb '07

04 Feb '07

Hi, The file swank-lispworks contains a function named dspec-file-position that, in recent LispWorks versions, reads forms from a file. The problem is that the file might contain #. forms that might refer to *compile-file-pathname* or *compile-file-truename*, or *load-pathname* or *load-truename*. In order to "emulate" the compilation or loading process, this function must also provide values to those variables so that the forms can be properly read. My quick fix is: (defun dspec-file-position (file dspec) (let ((*compile-file-pathname* (pathname file)) (*compile-file-truename* (truename file))) (let ((*load-pathname* *compile-file-pathname*) (*load-truename* *compile-file-truename*)) (with-open-file (stream file) (let ((pos #-(or lispworks4.1 lispworks4.2) (dspec-stream-position stream dspec))) (if pos (list :position (1+ pos) t) (dspec-buffer-position dspec 1))))))) Best regards, António Leitão.

2 1

[slime-devel] slime-apropos-package doesn't work with readtable-case = :invert
by Harald Hanche-Olsen 04 Feb '07

04 Feb '07

The subject says it all, I think. I run my lisps with (setf (readtable-case *readtable*) :invert) and if I try C-c C-d C-p cl-user <RET> I get the error: No such package: "CL-USER" The reason being as follows: slime-apropos-package calls slime-read-package-name which does a completing-read on the result of (swank:list-all-package-names t) which simply returns all package names as strings: In particular, they are all typically upper case. So the package name is passed to swank:apropos-list-for-emacs which calls (find-package (string-to-package-designator package)), and swank::string-to-package-designator passes the string through read-from-string, ending with a symbol whose name is all lower case. But :|cl-user| does not designated a package. Surely, there is some inconsistency, but I can't tell which part can be corrected without introducing another inconsistency. - Harald

3 6

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 04 Feb '07

04 Feb '07

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1063 slime/ChangeLog:1.1064 --- slime/ChangeLog:1.1063 Fri Feb 2 06:55:16 2007 +++ slime/ChangeLog Sat Feb 3 08:34:06 2007 @@ -1,8 +1,17 @@ +2007-02-03 Marco Baringer <mb(a)bese.it> + + * slime.el (slime-delete-swank-port-file): Fix typo in + warning message. + 2007-02-02 Marco Baringer <mb(a)bese.it> - * slime.el (slime-inferior-connect): Warn, as oposed to bailing - out with an error, when deleting the port file fails. Patch by: - Samium Gromoff <_deepfire(a)feelingofgreen.ru> + Warn, as oposed to bailing out with an error, when deleting the + port file fails. Patch by: Samium Gromoff + <_deepfire(a)feelingofgreen.ru> + + * slime.el (slime-delete-swank-port-file): New function. + (slime-inferior-connect): Use slime-delete-swank-port-file. + (slime-read-port-and-connect): Use slime-delete-swank-port-file. 2007-01-31 Marco Baringer <mb(a)bese.it>

1 0

[slime-devel] fork ?
by jan 03 Feb '07

03 Feb '07

I think Attila's enthusiasm for improving slime is great, however, I also think that some of the unspoken rules of open source have been broken here. These conventions are documented in ESR's 'Homesteading the Nooshere', but since that essay is rather long winded and philosophical I'll summarize here. 1. Attila, you're playing on Helmut's turf, you need to respect the ground rules set and also accept that Helmut has final say. 2. If you really, really can't abide by point 1 then you should create a proper fork. This means choosing a new name and creating a new project with its own mailing list. On your project website you should also try and justify the fork and the inevitable drain on developer resources. Note that forking due to trivialities is highly unlikely to attract other developers. Once you've forked, it's inappropriate to send suggestions to the slime mailing list. If you wish for slime to continue to improve, then release your fork under an open source license, but allow slime developers to port the changes they want. It's especially bad form to re-suggest changes you couldn't push through before the fork. http://article.gmane.org/gmane.lisp.slime.devel/5542 http://article.gmane.org/gmane.lisp.slime.devel/5788 http://article.gmane.org/gmane.lisp.slime.devel/5953 So I think Helmut's position is justified and not an overreaction (although an ultimatum is probably not the most effective course of action). My advice to Attila would be firstly to apologize, then either retract the fork or commit to it, the current situation cannot continue. just my 2c -- jan

4 3

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

03 Feb '07

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1062 slime/ChangeLog:1.1063 --- slime/ChangeLog:1.1062 Wed Jan 31 08:23:52 2007 +++ slime/ChangeLog Fri Feb 2 06:55:16 2007 @@ -1,3 +1,9 @@ +2007-02-02 Marco Baringer <mb(a)bese.it> + + * slime.el (slime-inferior-connect): Warn, as oposed to bailing + out with an error, when deleting the port file fails. Patch by: + Samium Gromoff <_deepfire(a)feelingofgreen.ru> + 2007-01-31 Marco Baringer <mb(a)bese.it> * slime.el (slime-repl-update-banner): Restore animation.

1 0

[slime-devel] [BUG] running under debian's emacs-snapshot
by Samium Gromoff 02 Feb '07

02 Feb '07

I'm not sure if it is a useful bugreport, but i'm trying to get my unicode workflow straight, which is why i tried running on emacs-snapshot. After starting slime i get this: <many many many> error in process filter: sldb-mode: Symbol's function definition is void: add-local-hook error in process filter: Symbol's function definition is void: add-local-hook </many many many> error in process filter: common-lisp-indent-function-1: Variable binding depth exceeds max-specpdl-size error in process filter: Variable binding depth exceeds max-specpdl-size slime is today's CVS, emacs is emacs-snapshot 20061218-1 regards, Samium Gromoff

1 0

[slime-devel] [PATCH] prevent failing delete-file from busting up the connection
by Samium Gromoff 02 Feb '07

02 Feb '07

This patch stop a failed port-information-file deletion from preventing slime to proceed with connection to swank. This helps to smooth the sbcl-suid workflow, when the setuid instance of sbcl creates a file which is then un-deleteable by slime running in an insufficiently privileged emacs process. regards, Samium Gromoff diff -urN slime-old/slime.el slime/slime.el --- slime-old/slime.el 2007-01-31 19:18:11.000000000 +0300 +++ slime/slime.el 2007-02-02 01:20:41.000000000 +0300 @@ -1596,7 +1596,9 @@ (defun slime-inferior-connect (process args) "Start a Swank server in the inferior Lisp and connect." (when (file-regular-p (slime-swank-port-file)) - (delete-file (slime-swank-port-file))) + (condition-case nil + (delete-file (slime-swank-port-file)) + (error nil))) (slime-start-swank-server process args) (slime-read-port-and-connect process nil)) @@ -1662,7 +1664,9 @@ (cond ((file-exists-p (slime-swank-port-file)) (let ((port (slime-read-swank-port)) (args (slime-inferior-lisp-args process))) - (delete-file (slime-swank-port-file)) + (condition-case nil + (delete-file (slime-swank-port-file)) + (error nil)) (let ((c (slime-connect slime-lisp-host port (plist-get args :coding-system)))) (slime-set-inferior-process c process))))

2 2

[slime-devel] Slime blows up with SBCL 1.0.2 on OS X/Intel
by Matt Pillsbury 02 Feb '07

02 Feb '07

Resent-From: mtbp(a)rci.rutgers.edu From: mtbp(a)rci.rutgers.edu Subject: Slime blows up with SBCL 1.0.2/Mac OS X Date: February 1, 2007 7:13:59 PM EST Resent-To: slime-devel(a)common-lisp.net To: slime-devel(a)common-lisp.net Hi, when I try to start the version of slime in CVS tarfile from the website using M-x slime (with SBCL 1.0.2 on OS X/x86 as my CL implementation), I get the following rather intimidating error message: === begin scary thing (progn (load "/Library/Application Support/Emacs/slime/slime/swank- loader.lisp" :verbose t) (funcall (read-from-string "swank:start- server") "/tmp/slime.7829" :coding-system "iso-latin-1-unix")) This is SBCL 1.0.2, an implementation of ANSI Common Lisp. More information about SBCL is available at <http://www.sbcl.org/>. SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. * ; loading #P"/Library/Application Support/Emacs/slime/slime/swank- loader.lisp" ; compiling file "/Library/Application Support/Emacs/slime/slime/ swank-backend.lisp" (written 19 DEC 2006 05:47:36 AM): Help! 11 nested errors. SB-KERNEL:*MAXIMUM-ERROR-DEPTH* exceeded. 0: (BACKTRACE 536870911 #<SYNONYM-STREAM :SYMBOL SB-SYS:*TTY* {100C9831}>) 1: ((LAMBDA NIL)) 2: ((LAMBDA NIL)) 3: (SB-IMPL::%WITH-STANDARD-IO-SYNTAX #<CLOSURE (LAMBDA NIL) {11CD7D6D}>) 4: (SB-IMPL::ERROR-ERROR) 5: (SB-IMPL::INFINITE-ERROR-PROTECTOR) 6: (ERROR TYPE-ERROR) Help! 11 nested errors. SB-KERNEL:*MAXIMUM-ERROR-DEPTH* exceeded. 0: (BACKTRACE 536870911 #<SYNONYM-STREAM :SYMBOL SB-SYS:*TTY* {11CE0E91}>) 1: ((LAMBDA NIL)) 2: ((LAMBDA NIL)) 3: (SB-IMPL::%WITH-STANDARD-IO-SYNTAX #<CLOSURE (LAMBDA NIL) {11CE0FAD}>) 4: (SB-IMPL::ERROR-ERROR) 5: (SB-IMPL::INFINITE-ERROR-PROTECTOR) ; ; compilation unit aborted ; caught 1 fatal ERROR condition ; compilation aborted after 0:00:01 6: * === end scary thing I have no idea what's going on here. I do know that SLIME seems to be working fine with CLISP, though. Many thanks, Matt

2 1

[slime-devel] Problem with SLIME-INPUT-STREAM and WITH-TIMEOUT (SBCL)
by Ariel Badichi 01 Feb '07

01 Feb '07

Hello, There seems to be a problem with SLIME-INPUT-STREAM in SLIME 2007-01-20 which causes the SLIME connection to break if the following steps are performed (using SBCL 1.0.1): 1. Evaluate (with-timeout 5 (read-line)) at the toplevel. 2. Wait; a timeout condition will be signalled. 3. Choose the continue restart. 4. Type something for read-line to return. Ariel

5 5

[slime-devel] slime-reindent-defun
by Gábor Melis 01 Feb '07

01 Feb '07

Consider this: (defmacro foo (x) "docstring" `(,x)) If I press C-U M-q in the docstring it ends up looking like this: (defmacro foo (x) "docstring" `(,x)) Strangely enough there is no problem with: (defmacro foo (x) "docstring" (list x)) Cheers, Gábor

2 1