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

[slime-devel] slime apparently mis-reporting closed connection
by Samium Gromoff 26 Oct '07

26 Oct '07

After well into the second decade of slime-disconnect/slime-connect loop iteration (interweaved with normal operation) the emacs side of slime stopped recognising connection status. I`m doing a slime-disconnect, restarting swank and slime-connect, however immediately after this either a slime-load-file or a (load ...) in slime repl result in a message "Connection closed." i have some time before i will have to reboot the machine, and until then i can provide various forensics upon request... regards, Samium Gromoff

5 5

[slime-devel] slime-apropos-package now sorts correctly
by Hoehle, Joerg-Cyril 20 Apr '07

20 Apr '07

Hi, slime-apropos-package now conforms to its specification and also sorts symbols printed with package prefix. I supply the patches as attachments in the hope that MS-Windows nor MS-Outlook will break the TAB and LF characters of the original diff. I hope this is fine. Regards, Jörg Höhle.

3 3

[slime-devel] slime-display-edit-hilights
by Marco Baringer 23 Dec '06

23 Dec '06

for those of you who don't follow c.l.l (which is probaly a good idea) i commited William Bland's patch[1]. see the ChangeLog for details. 1 - http://groups.google.com/group/comp.lang.lisp/browse_thread/thread/e1d0b7bf… -- -Marco Ring the bells that still can ring. Forget the perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen

8 20

[slime-devel] How to inspect locals
by Jonathon McKitrick 27 Aug '06

27 Aug '06

Hi all, when running SBCL and a condition occurs that causes a break, how can I view the locals that have been bound in the function? Viewing the arguments isn't hard, but I cannot seem to figure out the locals. -Jonathon -- "I am sure that Jesus would use a command prompt. Hello? Ten Commandments??"

12 17

[slime-devel] swank-sbcl patch: make swank-compile-string use compile-file
by Luís Oliveira 30 Jun '06

30 Jun '06

Hello, The following patch changes SBCL's swank-backend:swank-compile-string to create a temporary file and invoke compile-file on that similarly to what other backends, e.g. OpenMCL and Allegro, do. Everything seems to work fine but I haven't tested it extensively. Hopefully, it's not a terrible idea either. 2006-06-26 Luís Oliveira <loliveira(a)common-lisp.net> * swank-sbcl.lisp (tmpnam, temp-file-name): New functions. (swank-compile-string): Create temporary file with the string and compile-file it instead of compiling an anonymous lambda, as before, in order to better handle eval-when forms. -- Luís Oliveira luismbo (@) gmail (.) com http://student.dei.uc.pt/~lmoliv/

2 2

Re: [slime-devel] abcl problems
by Andras Simon 29 Jun '06

29 Jun '06

[I'm resending this because it bounced on Tuesday, due to the recent c-l.net troubles. Apologies if you get it twice. In the meantime I committed Helmut's patch to abcl.] On Tue, 27 Jun 2006, Helmut Eller wrote: > * Andras Simon [2006-06-27 12:03+0200] writes: > > > Anyway, I'd be grateful for any hints on how to start debugging this. > > At the lisp side we create a thread which periodically flushes some > output streams. We do this so that any buffered output shows up on > the Emacs side only after a short delay. > > We could work around the problem with (:write-string "") in our code, > if we test for empty strings. But the real problem seems to be that > ABCL's SlimeOutputStream writes the buffered text, but doesn't clear > the buffer afterwards. The following patch might be more appropriate: > > --- SlimeOutputStream.java.orig 2006-06-27 18:47:43.000000000 +0200 > +++ SlimeOutputStream.java 2006-06-27 19:48:44.000000000 +0200 > @@ -105,11 +105,12 @@ > > public void _finishOutput() throws ConditionThrowable > { > - try { > - LispThread.currentThread().execute(f, new SimpleString(stringWriter.toString())); > + super._finishOutput (); > + if (stringWriter.getBuffer().length() > 0) { > + String s = stringWriter.toString(); > + stringWriter.getBuffer().setLength(0); > + LispThread.currentThread().execute(f, new SimpleString(s)); > } > - catch (Throwable t) {} > - super._finishOutput(); > } > > public String toString() > This does the trick! Thanks, Helmut! Andras

1 0

[slime-devel] How to wrap code typed at the REPL?
by Philippe-André Lorin 29 Jun '06

29 Jun '06

I would like every expression I type at the REPL to be surrounded by a wrapper before evaluation. For instance, when I type: (+ 2 3) I want it to become: (wrap (+ 2 3)) How can I do that?

3 2

[slime-devel] abcl problems
by Andras Simon 27 Jun '06

27 Jun '06

I see the following with cvs slime/emacs/abcl: - After starting up slime/abcl, *slime-events* is getting filled up with (:write-string "") for no obvious reason. - If I compile a file (it doesn't matter what's in it) I get an endless stream of (:write-string "; Compiling /tmp/proba.lisp ...\n; (IN-PACKAGE #:CL-USER)\n; Wrote /tmp/proba.abcl (0.044 seconds)\n") in the *slime-events* buffer, and ; Compiling /tmp/proba.lisp ... ; (IN-PACKAGE #:CL-USER) ; Wrote /tmp/proba.abcl (0.044 seconds) in the repl. (But the compilation happens only once.) At first I thought this was related to Alan's recent (06/09) changes to swank-abcl.lisp, and going back to the previous version seemed to confirm this. But now, even though I removed the compiled files under ~/.slime/, I get the same problem with both the new (1.37) and the old (1.36) version. Strange. Anyway, I'd be grateful for any hints on how to start debugging this. Andras

1 0

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

26 Jun '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.914 slime/ChangeLog:1.915 --- slime/ChangeLog:1.914 Sun Jun 25 04:45:43 2006 +++ slime/ChangeLog Mon Jun 26 02:29:15 2006 @@ -1,3 +1,15 @@ +2006-06-26 Helmut Eller <heller(a)common-lisp.net> + + * swank-sbcl.lisp (find-definitions): Remove backward + compatibility code. + +2006-06-26 Luís Oliveira <loliveira(a)common-lisp.net> + + * swank-sbcl.lisp (tmpnam, temp-file-name): New functions. + (swank-compile-string): Create temporary file with the string and + compile-file it instead of compiling an anonymous lambda, as + before, in order to better handle eval-when forms. + 2006-06-25 Helmut Eller <heller(a)common-lisp.net> * swank-source-path-parser.lisp (suppress-sharp-dot): Return a

1 0

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

25 Jun '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.913 slime/ChangeLog:1.914 --- slime/ChangeLog:1.913 Sun Jun 18 14:22:30 2006 +++ slime/ChangeLog Sun Jun 25 04:45:43 2006 @@ -1,3 +1,17 @@ +2006-06-25 Helmut Eller <heller(a)common-lisp.net> + + * swank-source-path-parser.lisp (suppress-sharp-dot): Return a + unique symbol to avoid multiple entries for nil at toplevel in the + source-map. + + * slime.el (test compile-defun): Add a test for #. reader macro at + toplevel. + (slime-run-one-test): New command. + (sldb-activate): Recreate the sldb buffer if it doesn't + exist. (Can happen if someone kills the buffer manually.) + (slime-wait-condition): Add a dummy to slime-stack-eval-tags while + waiting so that the SLDB enters a recursive edit. + 2006-06-18 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> * slime.el (slime-echo-arglist): Simplify, just use slime-autodoc.

1 0