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 01 Jul '06

01 Jul '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 27 Jun '06

27 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 26 Jun '06

26 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

[slime-devel] Slime fails to report a compiler note
by Frédéric Jolliton 25 Jun '06

25 Jun '06

Hi, I'm new on this list. I don't know if the following problem was already reported. With Linux 2.6 (x86-32), SBCL 0.9.13 and Slime CVS (from today), I get the error below. Is there a compatibility problem between SBCL and Slime in this case ? (SBCL release vs Slime CVS) error while parsing arguments to DESTRUCTURING-BIND: invalid number of elements in ((1545 . 2005) (1988 . 2003) (1660 . 1950)) to satisfy lambda list ((SWANK-BACKEND::START . SWANK-BACKEND::END)): exactly 1 expected, but 3 found [Condition of type SB-KERNEL::ARG-COUNT-ERROR] Restarts: 0: [RETRY] Retry performing #<ASDF:COMPILE-OP NIL {B1A5C69}> on #<IRONCLAD-SYSTEM::IRONCLAD-SOURCE-FILE "common" {C51DBF1}>. 1: [ACCEPT] Continue, treating #<ASDF:COMPILE-OP NIL {B1A5C69}> on #<IRONCLAD-SYSTEM::IRONCLAD-SOURCE-FILE "common" {C51DBF1}> as having been successful. 2: [ABORT] Abort SLIME compilation. 3: [ABORT-REQUEST] Abort handling SLIME request. 4: [ABORT] Exit debugger, returning to top level. Backtrace: 0: (SWANK-BACKEND::SOURCE-PATH-SOURCE-POSITION (0 1 3 4) NIL #<HASH-TABLE :TEST EQ :COUNT 31 {BCB2321}>) 1: (SWANK-BACKEND::SOURCE-PATH-FILE-POSITION (7 1 3 4) #P"/usr/share/common-lisp/source/ironclad/common.lisp") 2: (SWANK-BACKEND::LOCATE-COMPILER-NOTE #P"/usr/share/common-lisp/source/ironclad/common.lisp" (7 1 3 4) " (LDB (BYTE 8 0) IRONCLAD::UB)") 3: (SWANK-BACKEND::COMPILER-NOTE-LOCATION #<SB-C::COMPILER-ERROR-CONTEXT >) 4: (SWANK-BACKEND::SIGNAL-COMPILER-CONDITION #<SB-INT:SIMPLE-COMPILER-NOTE {BCA1AB9}> #<SB-C::COMPILER-ERROR-CONTEXT >) 5: (SWANK-BACKEND::HANDLE-NOTIFICATION-CONDITION #<SB-INT:SIMPLE-COMPILER-NOTE {BCA1AB9}>) 6: (SIGNAL #<SB-INT:SIMPLE-COMPILER-NOTE {BCA1AB9}>) [..] -- Frédéric Jolliton

2 1

[slime-devel] connecting multiple users to one lisp process
by Joe Corneli 24 Jun '06

24 Jun '06

I am interested in connecting several uniquely-identified users to one lisp process. For example, the lisp process could be running a MUD and the users will be interacting with each other there. Someone mentioned to me that SLIME could be used to facilitate the "connection" aspect of this problem (perhaps still leaving some work in the unique identification of users). Any initial feedback or advice on how to approach this? Is SLIME the right tool for the job? If not, do you have any other suggestions? If yes, please advise on how to get started, and we'll talk more after that.

2 2

[slime-devel] BREAK in Lisp-mode buffers with OpenMCL
by graham＠gorgeous.org 24 Jun '06

24 Jun '06

Hi, When I call BREAK in a Lisp-mode buffer using OpenMCL, I don't get the Slime debugger. Instead I get OpenMCL's own debugger, which looks like this: ;;;; (break) ... > Break in process worker(7): > While executing: "Unknown" > Type :GO to continue, :POP to abort. > If continued: Return from BREAK. Type :? for other options. 1 > If I do the same thing from the REPL, I get the Slime debugger. I think I should get the Slime debugger in Lisp-mode as well. Obviously calling BREAK directly is not very useful, but when I insert breakpoints in functions by means of calls to BREAK I get the same behaviour. The behaviour depends on where the function is called, not on where it was compiled. I'm using OpenMCL Version 1.0 (DarwinPPC32) and recent CVS Slime and GNU Emacs. Emacs was started with emacs -q so I don't think there's anything funny in my setup. Graham

2 1

[slime-devel] upgraded clisp on cygwin, now slime won't load
by funkyj＠gmail.com 21 Jun '06

21 Jun '06

I had slime + clisp (on cygwin) working fine. Yesterday I decided to upgrade various cygwin packages (including clisp). Now when I try to start slime I get this error: ;; Loading file /home/jcano/.clisprc.lisp ... ;; Loaded file /home/jcano/.clisprc.lisp [1]> *** - LOAD: A file with name /c/cygwin/home/jcano/elisp/slime/2006-06-21/slime/swank-loader.lisp does not exist The following restarts are available: ABORT :R1 ABORT I tried picking up the latest SLIME (my previous slime was 2006-jan-20) but neither "fairly stable" nor "head" made any difference. I also blew away my ~/.slime directory in case that was stale (slime is no longer getting far enough to rebuild ~/.slime) but that didn't help. Yes, I looked in "~/elisp/slime/2006-06-21/slime" and it does indeed contain the file that Here is my current version of clisp; GNU CLISP 2.38 (2006-01-24) (built on winsteingoldlap.bluelnk.net [10.41.52.143]) Software: GNU C 3.4.4 (cygming special) (gdc 0.12, using dmd 0.125) gcc -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -O2 -fexpensive-optimizations -DUNICODE -DDYNAMIC_FFI -I. -x none -lintl libcharset.a libavcall.a libcallback.a -lreadline -lncurses -liconv -L/usr/local/libsigsegv-cygwin/lib -lsigsegv -L/usr/X11R6/lib -lX11 SAFETY=0 HEAPCODES STANDARD_HEAPCODES SPVW_PAGES SPVW_MIXED libsigsegv 2.2 libiconv 1.9 libreadline 5.0 Features: (READLINE REGEXP SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL COMMON-LISP LISP=CL INTERPRETER SOCKETS GENERIC-STREAMS LOGICAL-PATHNAMES SCREEN FFI GETTEXT UNICODE BASE-CHAR=CHARACTER PC386 UNIX CYGWIN) C Modules: (clisp i18n syscalls regexp readline) Installation directory: /usr/lib/clisp/ User language: ENGLISH Machine: I686 (I686) jcano-lt [192.168.1.103] I run slime like this M-x slime and this is in my .emacs: (defun slime () "load my .emacs_slime and run M-x slime" (interactive) (load-file "~/.emacs_slime") (slime)) .emacs_slime file: ;; -*- mode: emacs-lisp -*- (message "begin .emacs_slime") (setq inferior-lisp-program "clisp") (add-to-list 'load-path ;; CVS head (concat (getenv "HOME") "/elisp/slime/2006-06-21/slime") t) (require 'slime) (slime-setup) ;;; Configuration of Erik Naggum's HyperSpec access package. ;; If you have a local copy of the HyperSpec, set its path here. (setq common-lisp-hyperspec-root "file:///c:/cygwin/home/jcano/docs/CL/HyperSpec/") (setq common-lisp-hyperspec-symbol-table (concat (getenv "HOME") "/docs/CL/HyperSpec/ilisp/map_sym.txt" )) (message "end .emacs_slime") If I run clisp and execute the following command manually: [1]> (load "/c/cygwin/home/jcano/elisp/slime/2006-06-21/slime/swank-loader.lisp") *** - LOAD: A file with name /c/cygwin/home/jcano/elisp/slime/2006-06-21/slime/swank-loader.lisp does not exist The following restarts are available: ABORT :R1 ABORT Break 1 [2]> (load "/c:cygwin/home/jcano/elisp/slime/2006-06-21/slime/swank-loader.lisp") *** - PARSE-NAMESTRING: syntax error in filename "/c:cygwin/home/jcano/elisp/slime/2006-06-21/slime/swank-loader.lisp" at position 2 The following restarts are available: ABORT :R1 ABORT ABORT :R2 ABORT Break 2 [3]> abort Break 1 [2]> abort [4]> (load "/home/jcano/elisp/slime/2006-06-21/slime/swank-loader.lisp") ;; Loading file /home/jcano/elisp/slime/2006-06-21/slime/swank-loader.lisp ... ;; Compiling file /home/jcano/elisp/slime/2006-06-21/slime/swank-backend.lisp ... ;; Wrote file ;; /home/jcano/.slime/fasl/2006-06-18/clisp-2.38-unix-pc386/swank-backend.fas [... successful loading ...] I see in slime.el (eval-and-compile (defvar slime-path (let ((path (or (locate-library "slime") load-file-name))) (and path (file-name-directory path))) "Directory containing the Slime package. This is used to load the supporting Common Lisp library, Swank. The default value is automatically computed from the location of the Emacs Lisp package.")) ; ... (defun slime-init-command (port-filename coding-system) "Return a string to initialize Lisp." (let ((loader (if (file-name-absolute-p slime-backend) slime-backend (concat slime-path slime-backend))) (encoding (slime-coding-system-cl-name coding-system))) (format "%S\n%S\n\n" `(load ,loader :verbose t) `(swank:start-server ,port-filename :external-format ,encoding)))) OK, so CLisp wants file paths to be in cygwin/unix format (e.g. "/home/jcaon" and "/cygdrive/c/cygwin" etc.) but emacs (which is a win32 application) is providing a windows style "c:/cygwin/home/..." path which, somewhere along the way gets converted to "/c/cygwin/home/..." I can probably fix this by overriding slime-path (I'll try that after posting this). Does anyone know why upgrading (I think I had 2.35) to 2.38 would cause this failure? Can this be fixed so other noobs don't suffer the same problems I have? Regards, --jfc

1 1

Re: [slime-devel] Re: Unable to get SLIME working with sbcl-0.9.13
by rif 20 Jun '06

20 Jun '06

> > Ah, maybe I spoke too soon. Apparently, I need to set > > swank:*communication-style* to something other than :spawn. Is it known > > that :spawn doesn't work with sbcl? I somehow thought I'd been using > > :spawn with sbcl on my other (home) machine, but maybe I was confused. > > :spwan should work fine, but you need to build you SBCL with threads > enabled -- they are not built by default. Sorry, I'm confused. Looking at the SBCL build, the only thread relevant feature I found was :sb-thread, which does seem to me enabled by default in the x86 0.9.13 release (it's in *features*). In any case, I built a version from source where I explicitly enabled this feature. I'm not sure how to tell if I did it right, I put a customize-target-features.lisp file in the toplevel sbcl directory, right next to the base-target-features.lisp-expr file, and rebuilt. Using this version did not let SLIME work with :spawn. SLIME seems to start, and then immediately says "Process inferior-lisp hangup," and dies. rif

1 0

[slime-devel] swank reloading problem
by Cyrus Harmon 19 Jun '06

19 Jun '06

I'm trying to debug getting threads running on SBCL/x86/MacOS and in doing so I've come across a strange problem where something (presumably clim-desktop.asd) is requiring swank, which is causing swank.asd to get reloaded and swank-backend is getting recompiled, which causes current-thread to get redefined to 0. This seems to wreak havoc with some of the locking stuff, which presumably has various locks held while it's trying to output the results of the compilation. Should the definterface stuff in swank-backend have some sort of check to see if these haven't been previously implemented before overwriting the previous method definitions? Thanks, Cyrus

4 4

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

19 Jun '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.910 slime/ChangeLog:1.913 --- slime/ChangeLog:1.910 Sat Jun 17 12:11:04 2006 +++ slime/ChangeLog Sun Jun 18 14:22:30 2006 @@ -1,3 +1,20 @@ +2006-06-18 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> + + * slime.el (slime-echo-arglist): Simplify, just use slime-autodoc. + + * swank.lisp (arglist): Distinguish between provided actual args + and required formal args using the new slot provided-args. + (form-completion): Likewise. + (decoded-arglist-to-string): Use it here to display the argument + list (make-instance 'CLASS-NAME ...) rather + than (make-instance (quote CLASS-NAME) ...). + + * swank.lisp (extra-keywords change-class): Don't drop the first + argument. + + * slime.el (slime-parse-extended-operator-name): Don't move + point; fixes infinite loop. + 2006-06-17 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> * slime.el (slime-parse-extended-operator-name/cerror): Handle

1 0

[slime-devel] asdf-install kills slime
by Harald Hanche-Olsen 18 Jun '06

18 Jun '06

I was just going to try asdf-install for the very first time, and it turns out to kill slime. Or more precisely, my lisp and emacs both die (sbcl 0.9.13.21, GNU Emacs 23.0.0.1, slime from CVS as of 2006-06-04). So to get some more information, I tried again from the *inferioir-lisp* buffer (see beneath my signature, below). I figure the problem is with the debugger trying to print a string containing binary data, and somehow not using the UTF-8 encoding to do it. I have this charset specification in .emacs: (setf slime-lisp-implementations '((sbcl ("sbcl") :coding-system utf-8-unix) (cmucl ("cmucl") :coding-system iso-latin-1-unix))) - Harald PS. This is the wrong place to ask I know, but can anyone throw any light on the GPG message about "key id 0xNIL ()"? ---------------- This is SBCL 0.9.13.21, an implementation of ANSI Common Lisp. ;;; startup chatter elided * (require :asdf-install) ;;; somewhat verbose output elided * (asdf-install:install :cells) Install where? 1) System-wide install: System in /local/lib/sbcl/site-systems/ Files in /local/lib/sbcl/site/ 2) Personal installation: System in /Users/hanche/.sbcl/systems/ Files in /Users/hanche/.sbcl/site/ --> 1 Downloading 74072 bytes from http://common-lisp.net/project/cells/asdf-install/cells_2.0.tar.gz ... debugger invoked on a ASDF-INSTALL::KEY-NOT-TRUSTED: GPG warns that the key id 0xNIL () is not fully trusted Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [CONTINUE ] Install the package anyway 1: [SKIP-GPG-CHECK] Don't check GPG signature for this package 2: [ABORT ] Exit debugger, returning to top level. (ASDF-INSTALL::VERIFY-GPG-SIGNATURE/STRING "-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 (a whole bunch of binary data left out, all part of this humongous string) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (Darwin) iD8DBQFD1qcfl2RwVlDQtPYRApX/AKCFgsrLXsv8FllEQ1YQtC2nYRZiHACcDkJY whE3bSaRgquYThmepNzfYVc= =Pacw -----END PGP SIGNATURE----- " #P"/Users/hanche/CELLS.asdf-install-tmp")

1 1

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

18 Jun '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.908 slime/ChangeLog:1.910 --- slime/ChangeLog:1.908 Fri Jun 16 12:35:46 2006 +++ slime/ChangeLog Sat Jun 17 12:11:04 2006 @@ -1,3 +1,15 @@ +2006-06-17 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> + + * slime.el (slime-parse-extended-operator-name/cerror): Handle + cerror and change-class with :make-instance. + (slime-extended-operator-name-parser-alist): Handle change-class. + (slime-parse-extended-operator-name) + (slime-enclosing-operator-names): Fix the case when point is + within the operator. + + * swank.lisp (operator-designator-to-form): Handle cerror and + change-class with :make-instance. + 2006-06-16 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> * swank.lisp (operator-designator-to-form): Handle :cerror.

1 0

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

17 Jun '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.907 slime/ChangeLog:1.908 --- slime/ChangeLog:1.907 Wed Jun 14 10:58:37 2006 +++ slime/ChangeLog Fri Jun 16 12:35:46 2006 @@ -1,3 +1,16 @@ +2006-06-16 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> + + * swank.lisp (operator-designator-to-form): Handle :cerror. + (extra-keywords cerror): Make it work. + + * slime.el (slime-parse-extended-operator-name) + (slime-parse-extended-operator-name/make-instance) + (slime-parse-extended-operator-name/defmethod): New functions, + factored out from slime-enclosing-operator-names. + (slime-parse-extended-operator-name/cerror): New function. + (slime-extended-operator-name-parser-alist): New variable. + (slime-enclosing-operator-names): Use them here. + 2006-06-14 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> * slime.el (slime-goto-definition): If all definitions of a name

1 0

[slime-devel] Connect to remote lisp process
by Bruce L. Lambert, Ph.D. 16 Jun '06

16 Jun '06

>After seeing Marco Baringer's slime movie, I am trying to connect >from Emacs (v. 21.3.1) running on my Windows machine to cmucl >running on my Linux machine using the instructions provided by Andy >Sloane >(http://a1k0n.net/blah/archives/2005/11/04/T18_00_44/index.html). >All of the intermediate steps seem to be working, but when I try to >"M-x my-box-slime" I get the following error. > >error in process filter: byte-code: net-read error: >(cl-assertion-failed (plusp length)) >error in process filter: net-read error: (cl-assertion-failed (plusp length)) > >Any ideas? Thanks. I updated both slime and cmucl to latest versions and the error disappeared. Thanks. -bruce

1 0

[slime-devel] Fuzzy completion
by Levente Mészáros 16 Jun '06

16 Jun '06

Hi, Although I'm not a big emacs guru, so things might be implemented simpler, but I did what I could with a resonable effort. Still you may or may not find this useful. This is not a final patch for two reasons: first I'm not even sure it's worth it and if nobody is interested I will just keep it in my local repo. Second, it breaks current functionality: the one which continuously replaces text in the target buffer while you move up and down in the completion window with the current completion (selection). Personally I found that superfluous. So this is a somewhat different end user experience for fuzzy completion. It is a little bit closer to the other non fuzzy completion in that it does not take the focus away from the buffer you are editing and there are some other minor differences. I introduced a new minor mode called slime-fuzzy-target-buffer-completions-mode for the target buffer during fuzzy completion. You may find it usefull to bind your paredit open and close keys to (the ones bound to insert-parentheses and move-past-close-and-reindent) slime-fuzzy-select-and-process-event-in-target-buffer in the keymaps called slime-target-buffer-fuzzy-completions-map and slime-fuzzy-completions-map. Here is how it works (- means not yet implemented): When focus is in the target window (replace tab with your favorite key binding): + tab shows completion window if it was not open + tab updates completion window if there was editing since last time tab was pressed + tab implicitly completes if there's only one match + tab selects current completion if there were no editing since last tab (double tab) even if there are multiple matches + tab closes completion window if there are no matches at all - tab distinguishes between function and other symbols and puts an extra space before caret if mandatory parameters exists - tab puts the caret after the list in the target for unary function symbols + left/right moves caret in target window + up/down moves caret in completion window even though the focus is in the target window (changes current completion) + space/enter/(/) implicitly selects current completion and processes event in target window (paredit takes care about the rest) + normal editing operations allowed in target window - editing implicitly updates completion window in the background during editing (by a timer) + C-q closes completion window When focus is in the completion window: + cursor keys navigate + tab/mouse2 selects current completion and closes completion window + space/enter/(/) selects current completion, closes completion window and processes event in the target window + q closes completion window Cheers, levy -- There's no perfectoin

5 4

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

15 Jun '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.906 slime/ChangeLog:1.907 --- slime/ChangeLog:1.906 Sun Jun 11 07:02:08 2006 +++ slime/ChangeLog Wed Jun 14 10:58:37 2006 @@ -1,3 +1,9 @@ +2006-06-14 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> + + * slime.el (slime-goto-definition): If all definitions of a name + have the same location, go there directly rather than presenting + an xref buffer. + 2006-06-11 Douglas Crosher <dcrosher(a)common-lisp.net> * swank-scl (ext:stream-write-chars): update for SCL 1.3.

1 0

[slime-devel] Attempt to fix semantic indentation with clisp
by Damyan Pepper 15 Jun '06

15 Jun '06

This patch attempts to fix semantic indentation with clisp. I'm not sure how great an idea it is, but it seems to work for me. It works by changing the macro-functon on common-lisp:defmacro to one that also stores the arglist on the defined macro's symbol-plist. Strictly speaking, I don't believe you're meant to modify symbols in the common-lisp package in this way, but it seems to work with clisp. Any thoughts would be much appreciated! 2006-06-14 Damyan Pepper <damyanp(a)gmail.com> * swank-clisp.lisp: Replace common-lisp:defmacro with a modified version that stores the argument list in a way that can be retrieved with swank-backend:arglist. This makes semantic indentation work for macros with &body arguments. $ cvs -q diff -u Index: swank-clisp.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/swank-clisp.lisp,v retrieving revision 1.58 diff -u -r1.58 swank-clisp.lisp --- swank-clisp.lisp 22 Mar 2006 16:40:01 -0000 1.58 +++ swank-clisp.lisp 14 Jun 2006 11:47:00 -0000 @@ -137,12 +137,13 @@ (defimplementation arglist (fname) (block nil - (or (ignore-errors - (let ((exp (function-lambda-expression fname))) - (and exp (return (second exp))))) - (ignore-errors - (return (ext:arglist fname))) - :not-available))) + (or (get fname 'arglist) + (ignore-errors + (let ((exp (function-lambda-expression fname))) + (and exp (return (second exp))))) + (ignore-errors + (return (ext:arglist fname))) + :not-available))) (defimplementation macroexpand-all (form) (ext:expand-form form)) @@ -580,6 +581,22 @@ #+lisp=cl (ext:quit) #-lisp=cl (lisp:quit)) +♀ + +;;; Replace cl:defmacro with our own that stores the arglists +(defvar *old-defmacro* (copy-symbol 'common-lisp:defmacro t)) + +(defmacro defmymacro (&environment env &whole whole name params &body body) + (declare (ignore body)) + `(progn + (setf (get ',name 'swank-backend::arglist) ',params) + ,(funcall (macro-function *old-defmacro*) whole env) + ',name)) + +(setf *old-defmacro* (copy-symbol 'common-lisp:defmacro t)) +(setf (macro-function 'common-lisp:defmacro) (macro-function 'defmymacro)) + + ;;; Local Variables: ;;; eval: (put 'compile-file-frobbing-notes 'lisp-indent-function 1) ;;; eval: (put 'dynamic-flet 'common-lisp-indent-function 1)

3 4

[slime-devel] Problems with swank connection
by Henda Carvalho 13 Jun '06

13 Jun '06

Hi there, I´m using slime and I'm having a problem with the swank connection: (save-current-buffer (slime-disconnect) (if (get-buffer "*inferior-lisp*") (kill-buffer "*inferior-lisp*")) (slime) (if (not (slime-connected-p)) <error, do something> )) The problem is that the function 'slime-connected-p' is returning 'nil', meaning that there isn't a swank connection... Can somebody tell me why? I'm using windows xp, my lisp implementation is Allegro CL (version 7), and my Emacs is GNU Emacs 21.3.1. Best regards, Henda

4 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel June 2006