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

[slime-devel] Minor patch for slime-call-defun in slime.el
by Bill Clementson 21 Jan '07

21 Jan '07

I recently noticed that the comment for the "slime-call-defun" function comes after the "interactive" form. That doesn't cause any problems in the running of the function; however, it does mean that the comment doesn't appear when you do "C-h f slime-call-defun". The attached patch corrects this. -- Bill Clementson

1 0

Re: [slime-devel] Re: COPYRIGHT change - slime contributors please read this
by Luca Capello 20 Jan '07

20 Jan '07

Hello Peter! On Sat, 20 Jan 2007 04:59:01 +0100, Peter Seibel wrote: > Fine by me. If you're actually doing paperwork a la the FSF, drop me > an email and I'll send you my snail mail address. No paperwork, I'm simply trying to clearly define SLIME license. > Otherwise, I hereby place my past contributions to SLIME into the > public domain. Thank you :-) Thx, bye, Gismo / Luca

1 0

[slime-devel] slime-repl-defparameter
by Kilian Sprotte 20 Jan '07

20 Jan '07

Hi, this little patch makes slime-repl-defparameter functional again. (Correcting two typos. :) Cheers, Kilian Index: slime.el ========================================================== RCS file: /project/slime/cvsroot/slime/slime.el,v retrieving revision 1.748 diff -u -r1.748 slime.el --- slime.el 17 Jan 2007 15:44:29 -0000 1.748 +++ slime.el 17 Jan 2007 23:51:08 -0000 @@ -4473,10 +4473,10 @@ (defslime-repl-shortcut slime-repl-defparameter ("defparameter" "!") (:handler (lambda (name value) (interactive (list (slime-read-symbol-name "Name (symbol): " t) - (slime-read-from-minibuffer "Value: " "*"))) + (slime-read-from-minibuffer "Value: " :initial-value "*"))) (insert "(cl:defparameter " name " " value " \"REPL generated global variable.\")") - (slime-repl-send-input))) + (slime-repl-send-input t))) (:one-liner "Define a new global, special, variable.")) (defslime-repl-shortcut slime-repl-compile-and-load ("compile-and-load" "cl")

2 1

[slime-devel] slime-repl-defparameter
by Kilian Sprotte 20 Jan '07

20 Jan '07

My patch got corrupted, sorry.

1 1

Re: [slime-devel] Re: COPYRIGHT change - slime contributors please read this
by Luca Capello 19 Jan '07

19 Jan '07

Hello! This is only a remind for those who haven't yet answered, as I'm not sure that silent acceptance of Marco's commit could be considered valid. On Thu, 05 Oct 2006 00:48:04 +0200, Luca Capello wrote: > 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. These are still valid :-) > 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). Only Helmut Heller's advice is missing. >> doc/Makefile > > This was firstly created by Luke Gorrie at the same time of > doc/slime.texi and doc/texinfo-tabulate.awk, which clearly contain the > public domain statement (not the same for the copyright). I guess > that doc/Makefile is in the public domain as well, but we need Luke's > word. Modified by Peter Seibel and Christophe Rhodes. Michael Weber > provided the patch to create contributors.texi, > >> HACKING >> NEWS > > Both created by Luke and modified by Helmut. > >> PROBLEMS > > Created by Luke, modified by Helmut, Espen Wiborg and Christophe > Rhodes. Espen Wiborg already put its modifications in the PD. >> README > > Created by Luke, modified by Daniel Barlow, Helmut and Marco > Baringer. Thx, bye, Gismo / Luca

2 3

[slime-devel] ROOM bug?
by David Steuber 18 Jan '07

18 Jan '07

In the REPL buffer I entered the (ROOM) command: CL-USER> (room) Dynamic space usage is: 1,337,928,544 bytes. Read-only space usage is: 1,872 bytes. Static space usage is: 1,128 bytes. Control stack usage is: 3,008 bytes. Binding stack usage is: 576 bytes. Garbage collection is currently enabled. In SLDB buffer: The value 804013168 is not of type FIXNUM. [Condition of type TYPE-ERROR] Restarts: 0: [ABORT-REQUEST] Abort handling SLIME request. 1: [ABORT] Exit debugger, returning to top level. Backtrace: 0: ((LAMBDA (SB-VM::OBJ TYPE SB-VM::SIZE)) #<unavailable argument> #<unavailable argument> #<unavailable argument>) 1: (SB-VM::MAP-ALLOCATED-OBJECTS #<unavailable argument> #<unavailable argument>) 2: (SB-VM::TYPE-BREAKDOWN :DYNAMIC) 3: (SB-VM:MEMORY-USAGE) 4: (ROOM :DEFAULT) 5: (SB-INT:SIMPLE-EVAL-IN-LEXENV (ROOM) #<NULL-LEXENV>) 6: (SWANK::EVAL-REGION "(room) " T) 7: ((LAMBDA ())) 8: ((LAMBDA (SWANK-BACKEND::FN)) #<CLOSURE (LAMBDA #) {11C3DFB5}>) 9: (SWANK::CALL-WITH-BUFFER-SYNTAX #<CLOSURE (LAMBDA #) {11C3DFB5}>) 10: (SB-INT:SIMPLE-EVAL-IN-LEXENV (SWANK:LISTENER-EVAL "(room) ") #<NULL-LEXENV>) 11: ((LAMBDA ())) 12: ((LAMBDA (SWANK-BACKEND::HOOK SWANK-BACKEND::FUN)) #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA #) {11C3D8DD}>) 13: ((LAMBDA ())) 14: ((LAMBDA (SWANK-BACKEND::HOOK SWANK-BACKEND::FUN)) #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK> #<FUNCTION (LAMBDA #) {11822205}>) 15: (SWANK::CALL-WITH-REDIRECTED-IO #<SWANK::CONNECTION {1181E8C9}> #<CLOSURE (LAMBDA #) {11C3B2ED}>) 16: (SWANK::CALL-WITH-CONNECTION #<SWANK::CONNECTION {1181E8C9}> #<FUNCTION (LAMBDA #) {11822205}>) 17: (SWANK::HANDLE-REQUEST #<SWANK::CONNECTION {1181E8C9}>) 18: (SWANK::PROCESS-AVAILABLE-INPUT #<SB-SYS:FD-STREAM for "a constant string" {1181F1B1}> #<CLOSURE (LAMBDA #) {11C3B2D5}>) 19: ((FLET SWANK::HANDLER)) 20: ((LAMBDA (SWANK-BACKEND::_)) #<unused argument>) 21: (SB-IMPL::SUB-SERVE-EVENT NIL 0) 22: (SB-SYS:WAIT-UNTIL-FD-USABLE 0 :INPUT NIL) 23: (SB-IMPL::REFILL-BUFFER/FD #<SB-SYS:FD-STREAM for "standard input" {1181E211}>) 24: (SB-IMPL::INPUT-CHAR/UTF-8 #<SB-SYS:FD-STREAM for "standard input" {1181E211}> NIL #:EOF-OBJECT) 25: (READ-CHAR #<SB-SYS:FD-STREAM for "standard input" {1181E211}> NIL #:EOF-OBJECT #<unused argument>) 26: (READ-CHAR #<SYNONYM-STREAM :SYMBOL SB-SYS:*STDIN* {1000A1B1}> NIL #:EOF-OBJECT #<unused argument>) 27: (READ-PRESERVING-WHITESPACE #<SYNONYM-STREAM :SYMBOL SB-SYS:*STDIN* {1000A1B1}> NIL (NIL) T) 28: (READ-PRESERVING-WHITESPACE #<SYNONYM-STREAM :SYMBOL SB-SYS:*STDIN* {1000A1B1}> NIL (NIL) NIL) 29: (READ #<SYNONYM-STREAM :SYMBOL SB-SYS:*STDIN* {1000A1B1}> NIL (NIL) NIL) 30: (SB-IMPL::REPL-READ-FORM-FUN #<SYNONYM-STREAM :SYMBOL SB-SYS:*STDIN* {1000A1B1}> #<SYNONYM-STREAM :SYMBOL SB-SYS:*STDOUT* {10009BD9}>) 31: (SB-IMPL::REPL-FUN NIL) 32: ((LAMBDA ())) 33: ((LAMBDA ())) 34: (SB-IMPL::%WITH-REBOUND-IO-SYNTAX #<CLOSURE (LAMBDA #) {1181E0C5}>) 35: (SB-IMPL::TOPLEVEL-REPL NIL) 36: (SB-IMPL::TOPLEVEL-INIT) 37: ((LABELS SB-IMPL::RESTART-LISP)) SBCL 1.0.1 OS X PPC with SLIME 2006-12-24

1 0

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

18 Jan '07

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1053 slime/ChangeLog:1.1054 --- slime/ChangeLog:1.1053 Sun Jan 14 04:33:13 2007 +++ slime/ChangeLog Wed Jan 17 10:44:01 2007 @@ -1,3 +1,8 @@ +2007-01-17 Christian Lynbech <christian.lynbech(a)ericsson.com> + + * slime.el (slime-init-command): Use expanded files when writing + the LOAD form for swank. + 2007-01-14 Helmut Eller <heller(a)common-lisp.net> * slime.el: Cleanups for the repl history code.

1 0

[slime-devel] slime.el patch: swank path
by Christian Lynbech 17 Jan '07

17 Jan '07

I would like to propose the attached patch being added to slime.el. The problem it solves is in `slime-init-command', if the resulting loader path comes out with a "~/" in front some lisps (at least including SBCL and CMUCL will not be able to find swank. The solution is just to wrap an `expand-file-name' around `loader' in the load form generation. ------------------------+----------------------------------------------------- Christian Lynbech | christian #\@ defun #\. dk ------------------------+----------------------------------------------------- Hit the philistines three times over the head with the Elisp reference manual. - petonic(a)hal.com (Michael A. Petonic)

1 0

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

15 Jan '07

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1052 slime/ChangeLog:1.1053 --- slime/ChangeLog:1.1052 Fri Jan 12 10:27:10 2007 +++ slime/ChangeLog Sun Jan 14 04:33:13 2007 @@ -1,3 +1,34 @@ +2007-01-14 Helmut Eller <heller(a)common-lisp.net> + + * slime.el: Cleanups for the repl history code. + (slime-repl-mode-map): Don't shadow M-C-d. + (slime-repl-history-replace): Simplified. + (slime-repl-history-search-in-progress-p): New. + (slime-repl-position-in-history): If there's no match return + out-of-bound positions instead of nil. + (slime-repl-add-to-input-history): Never modify the argument. + (slime-repl-previous-input): Renamed from + slime-repl-previous-input-starting-with-current-input. + (slime-repl-next-input): Renamed from + slime-repl-next-input-starting-with-current-input + (slime-repl-forward-input): Renamed from slime-repl-next-input. + (slime-repl-backward-input): Renamed from + slime-repl-previous-input. + (slime-repl-history-pattern): Renamed from + slime-repl-matching-input-regexp. + (slime-repl-delete-from-input-history): Simplified. + + (slime-repl-history-map) + (slime-repl-history-navigation-neutral-commands) + (slime-repl-jump-to-history-item) + (slime-repl-previous-or-next-input) + (slime-repl-starting-with-current-input-regexp) + (slime-repl-continue-search-with-last-pattern) + (slime-repl-previous-or-next-matching-input): Deleted. + + (sldb-list-locals, sldb-list-catch-tags): Deleted. Aren't of much + use anymore. + 2007-01-12 Helmut Eller <heller(a)common-lisp.net> * swank-clisp.lisp: Better classification on frames on the stack.

1 0

[slime-devel] slime-texi patch
by Jeffrey Cunningham 15 Jan '07

15 Jan '07

[posting to correct list this time] Hmmm. This is strange. I was given commit privileges specifically for doing extensive work on doc/slime.texi. CVS lets me log in alright and seems to accept the changes - prompts me for comments and everything. But I just checked out a fresh copy and none of the changes I made this month (several sessions) are there. And yet, the changes I made in December are there (for example, the image on the front page). I don't know what to make of it. I'm going to post a patch to the list which incorporates the changes you made plus those I've made. (attached) Here's a changelog entry for it: 2007-01-14 Jeff Cunningham <jeffrey(a)cunningham.net> * doc/slime.texi: Update of function/key index with links. --Jeff On Sun Jan 14, 2007 at 07:54:38PM -0800, Bill Clementson wrote: > Hi Jeff, > > On 1/14/07, Jeffrey Cunningham <jeffrey(a)cunningham.net> wrote: > >On Sun Jan 14, 2007 at 05:10:32PM -0800, Bill Clementson wrote: > >> Attached is a patch for slime-texi. Here's the changelog entry: > >> > >> 2007-01-14 Bill Clementson <billclem(a)gmail.com> > >> > >> * doc/slime.texi: Cleanup of documentation typos/errors. > > > >Hi Bill; > > > >I noticed your patch is applied against doc/slime.texi from Jan 1 > >whereas I checked a number of changes into CVS for that file on Jan > >11. Should I do something beyond email the list that I have made > >changes? I am unfamiliar with what is customary in this list. Should I > >also send out a patch as you have done? > > > >I applied your patch to my current version and it worked fine. > > I did a cvs update before I made the changes to slime.texi, so my > patch should be against the latest version of slime.texi. Looking at > the changelog, it appears that the last patch to slime.texi was made > on 2006-12-24, so I don't know what happened to your changes. I just > did a "cvs co slime" as well to see what I got on a fresh install and > the date on slime.texi is also 2006-12-24. Perhaps your changes were > never applied? Since there are a limited number of people with commit > privileges, it's generally a good idea to double-check that any patch > that you email in is actually applied as sometimes they "fall through > the cracks". > > -- > Bill Clementson >

1 0