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

[slime-devel] clhs-lookup for reader macros
by Stas Boukarev 27 Feb '09

27 Feb '09

I added reader macros for hyperspec-lookup, hope this would be useful. -- With Best Regards, Stas.

2 1

[slime-devel] Problem with truncation of strings in debugger
by Jeff Workman 26 Feb '09

26 Feb '09

When I evaluate (format t "~A" (some-str-function)) on a longish string in debugger with E, the string is printed truncated, which seems like the wrong behavior to me. Also, surprisingly when I evaluate (setf *str* (some-str-function)) from debugger, the string stored in *str* is truncated as well. That suggests to me that the debugger is modifying the behavior of (format nil ...) or other functions I use in constructing strings used internally in my program, which would obviously be very bad and could interfere with operation of the program. I'm using SBCL 1.0.20 on Linux (and cvs slime) btw.

3 3

[slime-devel] Inspector doc
by Madhu 17 Jan '09

17 Jan '09

Helu, I'm having trouble using the inspector effectively: some objects are truncated, some lists are truncated etc. These boil down to bindings of printer variables [the debug state, etc] Can the inspector related variables be documented, and the rationale spelt out as to which output is being truncated, why, and under what circumstances? Could the hardcoded constants be documented as being hardcoded? I suspect this is not too much to ask if the new inspector is a "better thought out" replacement, the design could be explained in a few paragraphs in comments in the code or in a separate doc. I think it is an important enough component of SLIME to define the behaviour outside of the code which implements it. -- Madhu

4 8

[slime-devel] request for pecifying location fasl-files
by Knut Olav Bøhmer 10 Jan '09

10 Jan '09

Hi, I would like to be able to specify where slime should place it's fasl-files when running slime-compile-and-load-file. The location should be per-buffer/filename configurable by placing variable-definition in the header of a .lisp file or by a hook that runs when a .lisp file is opened. I have attached an example implementation that I use, and have used for a long time. It works for me. -- Free Software Consultant Cell: +47 - 47 34 40 08 Phone: +47 - 21 53 69 00, Fax: +47 - 21 53 69 09 Addr: Nydalsveien 30b, 0484 Oslo <http://www.freecode.no/>

5 4

[slime-devel] swank-listener-hooks fix, paredit-friendly REPL patch
by Ivan Shvedunov 12 Nov '08

12 Nov '08

Hello. I've discovered a problem with swank-listener-hooks (rendering REPL unusable), which is needed for CLG. The trivial patch that restores it's functionality is attached. Another patch attached to this message makes SLIME REPL usable in Paredit mode by using the part of input between its start and (point) as history search pattern. I've sent a patch doing that long time ago, it was applied but later accidentally (as I understood it after asking on #lisp) reverted. I forgot about it for a while and just kept changes in my copy of SLIME, but now I decided to share them again. Thanks. Ivan

4 10

[slime-devel] slime has broken cmucl mp
by Madhu 01 Nov '08

01 Nov '08

It used to be possible to run multiprocessing servers like a webserver which coexisted with slime. This is no longer possible With current CVS slime, swank's WAIT-FOR-EVENT blocks all other processes from handling FD events There is a simple test case, but here is a more realistic one: I'm attaching a program "t2.lisp" which seeks to illustrates the problem. This is a simple program which listens on a port [8128 by default] and prints a message to clients which connect to it. -- In a bare lisp * (load "t2.lisp") LISTEN-FOR-CONNECTIONS creates a process which listens at port 8128. -- run `telnet localhost 8128' from a shell, a few times. This will result in the bogus service printing a message to the telnet client, as expected. -- load slime in the lisp, and listen at port 4005 * (load "/path/to/swank-loader.lisp") * (swank-loader::init) * (swank::setup-server 4005 #'print nil nil (swank::find-external-format "latin-1-unix")) -- Connect to the lisp from emacs using M-x slime-connect localhost 4005 -- run `telnet localhost 8128' from a shell. This hangs until the slime connection exits. This is a serious problem, and exposes many issues with SLIME's design. -- Madhu

2 4

[slime-devel] q in sldb doesn't quit anymore
by Raymond Toy 01 Nov '08

01 Nov '08

In the latest CVS build of slime, pressing "q" in sldb doesn't abort anymore. I get another error. Pressing "a" does abort. I hope this wasn't an intentional change. I have "q" hardwired now, so changing to "a" will be hard. :-( Ray

2 2

[slime-devel] CVS Snapshot Link Broken
by Elliott Slaughter 31 Oct '08

31 Oct '08

Hi, The link to the CVS snapshot ( http://common-lisp.net/cgi-bin/viewcvs.cgi/root.tar.gz?root=slime&view=tar) gives me a 403 Forbidden error. It would be nice if this link worked, especially for Windows users who may not have CVS installed. Thanks. -- Elliott Slaughter "Any road followed precisely to its end leads precisely nowhere." - Frank Herbert

2 2

[slime-devel] sb-impl::indenting-streams on the chopping block
by Nikodemus Siivola 31 Oct '08

31 Oct '08

Aside from slime/contrib/swank-presentations.lisp (or (and (typep stream 'sb-impl::indenting-stream) (slime-stream-p (sb-impl::indenting-stream-stream stream))) (and (typep stream (find-symbol "PRETTY-STREAM" 'sb-pretty)) (find-symbol "ENQUEUE-ANNOTATION" 'sb-pretty) (not *use-dedicated-output-stream*) (slime-stream-p (sb-pretty::pretty-stream-target stream))))) SB-IMPL::INDENTING-STREAM is, as far as I can tell, otherwise unused. Does someone actually use them? Any objections to deleting them? (And the first leg of the OR in Slime.) Cheers, -- Nikodemus

2 2

[slime-devel] Auto-jumping to compiler notes
by Jeff Workman 31 Oct '08

31 Oct '08

I noticed that there seems to have been a recent change to SLIME that makes it jump to compiler notes automatically when a file is compiled. Also, it seems to jump even to SBCL compiler optimization notes, which makes it very annoying to work on files where I have speed declarations. I don't like the auto-jumping in general, since there are times I might have a warning in a file temporarily while working on something else in the file, and people can just run slime-next-note manually if they want to see the notes, but at a minimum it shouldn't apply to optimization notes. Or if you don't want to change the default behavior, is there a variable I can set to disable it?

2 1

[slime-devel] Problem with `slime-popup-buffer-quit' in XEmacs
by Steven E. Harris 30 Oct '08

30 Oct '08

I've noticed this problem in XEmacs, but not in Emacs. When one macroexpands a form, the frame splits, the "*SLIME Macroexpansion*" window appears, and the cursor jumps there. If one then presses 'q' -- bound to `slime-popup-buffer-quit-function' (which is bound to `slime-popup-buffer-quit' in the buffer), not only does the macroexpansion buffer's window close, but the original window that contained the form that was macroexpanded gets buried as well. That is, quitting from the macroexpansion buffer does not return to the original buffer; it returns to what I guess is one buffer below that original buffer in the stack. -- Steven E. Harris

2 2

[slime-devel] swank+sbcl and cpu utilization
by Chris Goellner 30 Oct '08

30 Oct '08

I'm trying to get a remote SWANK+SBCL setup going and I've hit a snag. Everything works and I can connect to the running SBCL. However, when I disconnect the SBCL process drives the CPU to 100%. I've tried this on OS X 10.5, Solaris 2.8, and Linux Ubuntu with SBCL 1.0.20. I've checked that the slime on the remote and local ends are the same version which is the latest from the CVS. My guess is I'm doing something obviously wrong since it looks like a lot of people use this setup without a problem. So, few that I could only find one Google entry that seemed on point but the recommended change is to a function that isn't in my version of slime. my .emacs file looks like: (add-to-list 'load-path "path/to/slime") (setq inferior-lisp-program "/usr/local/bin/sbcl") (require 'slime) (slime-setup) and my .sbclrc file looks like: (require 'asdf) (require 'asdf-install) I've got another file called swank.lisp that starts up my remote side sbcl+swank process: (asdf:oos 'asdf:load-op 'swank) (setf swank:*communication-style* :fd-handler) (setf swank:*use-dedicated-output-stream* nil) (swank:create-server :dont-close t) I call this file as 'sbcl --load swank.lisp' and the whole system works great. Until I disconnect from the sbcl instance. Then it spikes the CPU and will spin until I stop it. I've got this working in CLISP but I've been using SBCL and I would like to have both working. Any suggestions?

2 2

[slime-devel] Problems with slime-edit-definition
by Yarek Kowalik 28 Oct '08

28 Oct '08

I've recently (3 weeks ago) updated slime from CVS, and now the M-. command no longer works for me. I am no longer able to "drill-down" on the definition of a CLOS class, for example, and jump to the source file. I'm using SBCL 1.0.20 on x86. I'm working with Weblocks source code if that matters. This is was one of the features I used very frequently, and not having it is a serious handicap. Any suggestions on how to make it work would be much appreciated. Thanks, Yarek

2 4

[slime-devel] Simplifying backtraces in the debugger
by Steven E. Harris 27 Oct '08

27 Oct '08

I'm not sure if this grievance falls to CLISP or to SLIME. When I land in the debugger, there are way too many frames present. Most of them are just noise, and I usually can't find the interesting frames -- such as those corresponding to named functions that I wrote -- with lexical bindings to inspect. Playing around with CLISP outside of SLIME, I see that one can set the mode used by the ":bt" command in the debugger. This can help to simplify the output, though I haven't yet figured out which of the five modes corresponds to what I'd /like/ to see. Consider this contrived example: ,---- | CL-USER> (defun foo (n) | (/ 3 n)) | FOO | CL-USER> (foo 0) `---- Evaluating that second form provokes this view in the debugger: (Take a deep breath.) ,---- | /: division by zero | [Condition of type SYSTEM::SIMPLE-DIVISION-BY-ZERO] | | Restarts: | 0: [RETRY] Retry SLIME REPL evaluation request. | 1: [ABORT] Return to SLIME's top level. | 2: [CLOSE-CONNECTION] Close SLIME connection | 3: [ABORT] Abort main loop | | Backtrace: | 0: [366] frame binding variables (~ = dynamically): | | ~ SWANK::*SLDB-STEPPING-P* <--> NIL | 1: [363] frame binding variables (~ = dynamically): | | ~ SWANK::*SLDB-LEVEL* <--> 0 | 2: [360] frame binding variables (~ = dynamically): | | ~ *PACKAGE* <--> #<PACKAGE COMMON-LISP-USER> | 3: <1/354> #<COMPILED-FUNCTION SWANK::DEBUG-IN-EMACS> | [353] frame binding variables (~ = dynamically): | | ~ SWANK::*SLIME-INTERRUPTS-ENABLED* <--> T | 4: <1/347> #<COMPILED-FUNCTION SWANK:INVOKE-SLIME-DEBUGGER> | - #<COMPILED-FUNCTION SWANK::SWANK-DEBUGGER-HOOK-1> | 5: <1/345> #<COMPILED-FUNCTION SWANK::SWANK-DEBUGGER-HOOK-1> | - #<COMPILED-FUNCTION SWANK::SWANK-DEBUGGER-HOOK-1> | 6: [344] frame binding variables (~ = dynamically): | | ~ *DEBUGGER-HOOK* <--> NIL | 7: <1/340> #<COMPILED-FUNCTION #:|624 629 (DEFINTERFACE CALL-WITH-DEBUGGER-HOOK (HOOK FUN) ...)-61-3-1|> | - #<COMPILED-FUNCTION #:|624 629 (DEFINTERFACE CALL-WITH-DEBUGGER-HOOK (HOOK FUN) ...)-61-3-1|> | 8: <1/335> #<COMPILED-FUNCTION SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK> | - #(NIL #<SYSTEM::SIMPLE-DIVISION-BY-ZERO #x10140B4D>) | 9: <1/331> #<COMPILED-FUNCTION SWANK:SWANK-DEBUGGER-HOOK> | [329] frame binding variables (~ = dynamically): | | ~ *DEBUGGER-HOOK* <--> #<COMPILED-FUNCTION SWANK:SWANK-DEBUGGER-HOOK> | 10: <1/326> #<SYSTEM-FUNCTION INVOKE-DEBUGGER> 1 | [325] frame binding variables (~ = dynamically): | | ~ SYSTEM::*PRIN-STREAM* <--> #<UNBOUND> | 11: [322] frame binding variables (~ = dynamically): | | ~ *PRINT-READABLY* <--> NIL | 12: [319] frame binding variables (~ = dynamically): | | ~ *PRINT-ESCAPE* <--> T | 13: <1/315> #<SYSTEM-FUNCTION /> 2 | - 3 | 14: [313] EVAL frame for form (/ 3 N) | Locals: | N = 0 | 15: [309] frame binding environments | VAR_ENV <--> NIL | FUN_ENV <--> NIL | BLOCK_ENV <--> NIL | GO_ENV <--> NIL | DECL_ENV <--> ((DECLARATION OPTIMIZE DECLARATION)) | 16: [303] frame binding variables #<ADDRESS #x7FF404FC> binds (~ = dynamically): | | N <--> 0 | Next environment: NIL | 17: [297] APPLY frame for call (FOO '0) | 18: <1/293> #<FUNCTION FOO (N) (DECLARE (SYSTEM::IN-DEFUN FOO)) (BLOCK FOO (/ 3 N))> 1 | - #<FUNCTION FOO (N) (DECLARE (SYSTEM::IN-DEFUN FOO)) (BLOCK FOO (/ 3 N))> | 19: [292] EVAL frame for form (FOO 0) | 20: [289] frame binding environments | VAR_ENV <--> NIL | FUN_ENV <--> NIL | BLOCK_ENV <--> NIL | GO_ENV <--> NIL | DECL_ENV <--> ((DECLARATION OPTIMIZE DECLARATION)) | 21: <1/284> #<SYSTEM-FUNCTION EVAL> | - (FOO 0) `---- If I ran across this output in a large program, I'd probably be most interested in frame 14, where the division operator is being evaluated. Expanding it shows that "N" was bound to 3. Is there some way to configure SLIME to sift through these frames and reduce them to something more "interesting"? For instance, by my criteria, everything in frames 1 through 12 above is irrelevant to the debugging intent, unless I was trying to debug the debugger. As an aside, I'd appreciate any comparison in the output to other implementations besides CLISP. Are they less chatty? -- Steven E. Harris

2 2

[slime-devel] slime.el requires arc-mode
by Steven E. Harris 27 Oct '08

27 Oct '08

Line 4603 in slime.el contains the following form: ,---- | ((:zip file entry) | (require 'arc-mode) | (set-buffer (find-file-noselect file t)) | (goto-char (point-min)) | (re-search-forward (concat " " entry "$")) | (let ((buffer (save-window-excursion | (archive-extract) | (current-buffer)))) | (set-buffer buffer) | (goto-char (point-min)))) `---- Note that it requires arc-mode. I don't have arc-mode, so slime.el won't load in XEmacs. Is this a new prerequisite for running SLIME? -- Steven E. Harris

3 5

[slime-devel] ASDF contrib always reports "Compilation failed" in the minibuffer
by Mark Evenson 22 Oct '08

22 Oct '08

The 'slime-asdf' contribution always reports "Compilation failed" in the minibuffer for all of the various REPL shortcut commands (i.e. those prefixed with the "'" character) dealing with ASDF (tested this under SBCL, ABCL, and CLISP). This is occurring because the value of ASDF:OPERATE (aka ASDF:OOS) is seemingly always NIL. COLLECT-NOTES in swank.lisp:2461 is passing this result back to SLIME in the COMPILATION-RESULT to be reported in the minibuffer as status. Did something get lost in a refactoring somewhere? Or did the ASDF hooks always have this behavior? I can't see a plausible way to assign a meaningful status from ASDF:OPERATE anyways (my understanding is that it always returns nil), so my suggestion would be to change the minibuffer message for COMPILATION-RESULTs from ASDF invocations, but that didn't look like a fast fix, so I wanted to solicit advice. In the scale of things, this is a minor cosmetic problem with SLIME, but it was bugging me (and would be confusing for new users)… -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."

2 1

[slime-devel] Current slime head broken on alisp.
by Luke Hope 21 Oct '08

21 Oct '08

Confirmed with a user on #lisp. Both alisp and acl-express. In *slime-scratch*, try evaluating (+ 1 'foo) with C-x C-e. The swank-debugger fails to come up. It works fine in SBCL and Clojure. Also, does anyone know what happened to the little "eval..." message in the emacs status bar when the lisp is working? That was extremely useful to me. -Luke

2 2

[slime-devel] [patch] slime-end-of-defun complain "Symbol's value as variable is void: major"
by S.P.Tseng 21 Oct '08

21 Oct '08

Follow function in file "slime-editing-commands.el", should use "major-mode" instead of "major". It seems variable "major" in emacs23 is deprecated. ,---- | (defun slime-end-of-defun () | (interactive) | (if (eq major 'slime-repl-mode) | (slime-repl-end-of-defun) | (end-of-defun))) | `---- -- The opposite of love is not hate; the opposite of love is solitude.

2 1

[slime-devel] patch for ABCL to (more) correctly report source location for COMPILE-CONDITION
by Mark Evenson 19 Oct '08

19 Oct '08

swank-abcl.lisp (handle-compile-warning): Report source location position when we can. Use NAMESTRING for *compile-filename*. -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now." Index: swank-abcl.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/swank-abcl.lisp,v retrieving revision 1.58 diff -u -r1.58 swank-abcl.lisp --- swank-abcl.lisp 17 Oct 2008 21:26:53 -0000 1.58 +++ swank-abcl.lisp 19 Oct 2008 15:02:17 -0000 @@ -127,7 +127,6 @@ (defimplementation local-port (socket) (java:jcall (java:jmethod "java.net.ServerSocket" "getLocalPort") socket)) - (defimplementation close-socket (socket) (ext:server-socket-close socket)) @@ -263,7 +262,6 @@ (defimplementation frame-locals (index) `(,(list :name "??" :id 0 :value "??"))) - (defimplementation frame-catch-tags (index) (declare (ignore index)) nil) @@ -306,8 +304,11 @@ (in-package :swank-backend) (defun handle-compiler-warning (condition) - (let ((loc nil));(getf (slot-value condition 'excl::plist) :loc))) - (unless (member condition *abcl-signaled-conditions*) ; filter condition signaled more than once. + (let ((loc (when (and jvm::*compile-file-pathname* + system::*source-position*) + (cons jvm::*compile-file-pathname* system::*source-position*)))) + ;; filter condition signaled more than once. + (unless (member condition *abcl-signaled-conditions*) (push condition *abcl-signaled-conditions*) (signal (make-condition 'compiler-condition @@ -325,7 +326,7 @@ (list :position (1+ pos))))) (t (make-location - (list :file *compile-filename*) + (list :file (namestring *compile-filename*)) (list :position 1))))))))) (defvar *abcl-signaled-conditions*)

2 1

[slime-devel] Swank sbcl error - patch attached
by jcm＠sdf.lonestar.org 17 Oct '08

17 Oct '08

Type fixed: Index: swank-sbcl.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/swank-sbcl.lisp,v retrieving revision 1.224 diff -u -r1.224 swank-sbcl.lisp --- swank-sbcl.lisp 16 Oct 2008 21:15:28 -0000 1.224 +++ swank-sbcl.lisp 17 Oct 2008 17:18:29 -0000 @@ -467,7 +467,7 @@ (defimplementation swank-compile-file (pathname load-p external-format) (handler-case - (multiple-value-bind (output-file warnigns-p failure-p) + (multiple-value-bind (output-file warnings-p failure-p) (with-compilation-hooks () (compile-file pathname :external-format external-format)) (values output-file warnings-p

2 1

[slime-devel] swank-require not implemented in kawa (current svn)
by Matthew D. Swank 16 Oct '08

16 Oct '08

I know kawa is not a regularly supported back end, but could someone give me away around: java.lang.Error: swank-require not implemented [type java.lang.Error] Restarts: 0: [quit] terminate current thread Backtrace: 0: ferror$V ("~a not implemented" ["swank-require"]) 1: lookupSlimefun (|swank:swank-require| gnu.kawa.slib.srfi$Mnhash$Mntable@ca56214) 2: $PcEval ((|swank:swank-require| (quote ({(keywords)}swank-asdf {(keywords)}swank-package-fu {(keywords)}swank-fuzzy {(keywords)}swank-fancy-inspector {(keywords)}swank-arglists))) #<environment user>) 3: listenerLoop (chan@b035079 #<environment user> #<output-port>) 4: listener (chan@b035079 #<environment user>) 5: lambda6 (chan@b035079) 6: apply1 (#<procedure gnu.expr.ModuleMethod> chan@b035079) 7: applyN (#<procedure gnu.expr.ModuleMethod> [chan@b035079]) 8: applyN ([chan@b035079]) 9: applyN ([#<procedure gnu.expr.ModuleMethod> chan@b035079]) 10: apply2 (#<procedure gnu.expr.ModuleMethod> chan@b035079) 11: lambda55 () 12: apply0 (#<procedure gnu.expr.ModuleMethod>) 13: apply0 () 14: run () 15: run () Locals: this = Thread[swank-listener,5,main] Thanks, Matt -- "You do not really understand something unless you can explain it to your grandmother." -- Albert Einstein.

1 1

[slime-devel] backtrace write-string to wrong stream
by Willem Broekema 16 Oct '08

16 Oct '08

(For some reason a previous copy of this mail did not make it to the list.) Some backtrace output ended up in the REPL buffer. - Willem --- swank.lisp 03 Oct 2008 16:45:57 +0200 1.597 +++ swank.lisp 04 Oct 2008 12:43:27 +0200 @@ -120,7 +120,7 @@ (#\return (write-string "\\r" stream)) (t (write-char c stream)))) (write-char #\" stream)) - (t (write-string string))))) + (t (write-string string stream))))) (set-pprint-dispatch 'string #'escape-string 0 table) table)))

2 1

[slime-devel] getting emacs debugger in latest slime with Allegro...?
by Gary King 16 Oct '08

16 Oct '08

This is with the cvs head of slime and Allegro Common Lisp. Not always but often, when I choose to compile a file via c-x c-k, the compile happens and then I get tossed in the emacs lisp debugger with a message similar to: Debugger entered: nil (condition-case error (slime-net-read) (error (debug) (slime-net- close process t) (error "net-read error: %S" error))) slime-net-read-or-lose(#<process SLIME Lisp>) slime-process-available-input(#<process SLIME Lisp>) slime-net-filter(#<process SLIME Lisp> "000029(:write-string \"; No value\" :repl-result)000017(:return (:ok nil) 961)") once this has happened, just about every interaction with slime provides the same (or similar) bug. To stop it, I must quick the slime session and restart it. This started happening a few days ago after I updated. It's very irritating. (to say the least) -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM

2 1

[slime-devel] a different flashing function for `slime-compile-region'
by Yoni Rabkin 13 Oct '08

13 Oct '08

Hello, This patch to slime.el makes the `slime-compile-region' flash a more subtle effect. I'm using it, and thought that someone else might enjoy it as well. Maybe a cleaner implementation would be to call a `slime-flashing-function', to allow different flashing styles to be changed more easily. -- "Cut your own wood and it will warm you twice"

1 0

[slime-devel] Kawa Support
by Volkan YAZICI 12 Oct '08

12 Oct '08

Hi, Is there problem with the contrib/swank-kawa.scm? COMPILE-FILE in Kawa 1.9.1 REPL complains that gnu.text.SyntaxException: /home/vy/elisp/slime/contrib/swank-kawa.scm:2062:1: '(* 1 st$unit)' is not a valid identifier at kawa.lib.system.compileFile(system.scm:94) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at gnu.expr.PrimProcedure.apply(PrimProcedure.java:251) at gnu.mapping.CallContext.runUntilDone(CallContext.java:251) at gnu.expr.ModuleExp.evalModule(ModuleExp.java:296) at kawa.Shell.run(Shell.java:230) at kawa.Shell.run(Shell.java:172) at kawa.Shell.run(Shell.java:159) at kawa.repl.main(repl.java:844) Regards.

3 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel October 2008