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

[slime-devel] features from ILisp I miss in slime
by Rodrigo Ventura 24 Nov '04

24 Nov '04

Hello all, I've just tryed slime, after years of ILisp use, and I feel great! Slime is definitely a step ahead of ILisp. However, there some features I was used to in ILisp, and that I miss in slime. Maybe some of them are configurable, maybe others are not. Here goes my list: - there are a list of key bindings that can be seen after a C-h m in a Lisp Slime mode, which do not work (e.g., C-c C-a, C-c C-c, etc.) Some of them have different key bindings in Slime, while others follow a distinct functional scheme (e.g., showing arguments as you type, which works fine in slime). - in Lisp Slime mode a RET does not auto-indent the next line. It'd be useful to have auto-identation, so that we could save a TAB everytime we write a new line of LISP. - in the REPL loop M-p is not quite pratical; couldn't you use for instance C-up for last expression entered (similar to ILisp)? Cheers, Rodrigo -- *** Rodrigo Martins de Matos Ventura <yoda(a)isr.ist.utl.pt> *** Web page: http://www.isr.ist.utl.pt/~yoda *** Teaching Assistant and PhD Student at ISR: *** Instituto de Sistemas e Robotica, Polo de Lisboa *** Instituto Superior Tecnico, Lisboa, PORTUGAL *** PGP fingerprint = 0119 AD13 9EEE 264A 3F10 31D3 89B3 C6C4 60C6 4585

7 7

[slime-devel] C-c C-l bug
by Surendra Singhi 24 Nov '04

24 Nov '04

Hi, This time I am using slime standard 1-0 release on Xemacs(with clisp) and it seems the command for loading a file doesn't work, specifically the short-cut key and the associated command. It doesn't do anything rather shows the *inferior-lisp* buffer for no reason. The explicit lisp load file command works without any problem. Thanks in advance -- Surendra Singhi www.public.asu.edu/~sksinghi

3 7

[slime-devel] xemacs & slime - bug
by Surendra Singhi 22 Nov '04

22 Nov '04

I use xemacs and slime on windows machine. I recently downloaded the latest version of slime from cvs, but while starting it I get the following error message. Any help on this will be appreciated. I looked into the code and was able to figure out the problem somewhere in slime.el file. But I am a slime and xemacs newbie and wasn't able to fix it. Signaling: (error "No such coding system" iso-8859-1-unix) set-process-coding-system(#<network connection "*lisp-output-stream*<1>" (1533 . "127.0.0.1") state:run> iso-8859-1-unix iso-8859-1-unix) (let ((stream ...)) (when slime-kill-without-query-p (process-kill-without-query stream)) (set-process-filter stream (quote slime-output-filter)) (set-process-coding-system stream slime-net-coding-system slime-net-coding-system) stream) slime-open-stream-to-lisp(1533) slime-dispatch-event((:open-dedicated-output-stream 1533) #<network connection "SLIME Lisp<1>" (1531 . "127.0.0.1") state:run>) slime-process-available-input() slime-net-filter(#<network connection "SLIME Lisp<1>" (1531 . "127.0.0.1") state:run> "\n") Thanks in advance, Surendra Singhi

2 2

[slime-devel] installing slime on windows with emacs 21.3
by Jason Wang 22 Nov '04

22 Nov '04

hi, i read the installation instructions, one point i does not understand, which is: "installation just requires a few lines in your '~/.emacs':" where is the '~/.emacs' in windows distribution of emacs? please enlighten me on this, thanks alot! Jason -- www.programer.name - my own personal blog : )

5 4

[slime-devel] SLIME debugger and local vars
by Lynn Quam 22 Nov '04

22 Nov '04

I have been using the SLIME debugger extensively with CMUCL and ALlegro 6.0. I find the SLIME debugger to be a big improvement over the "native" Lisp debuggers. One of the biggest improvements is having a uniform debugger and inspector interface for the different Lisps. Here is my question: In Allegro, with (declaim (optimize (safety 3)(space 1)(speed 2)(debug 2))) I find that most of the local variables are available in the SLIME debugger, but that the variable names are lost. The debugger prints something like: 13: ((METHOD INTERSECT-CURVE-WITH-DTM ...) Locals: TERRAIN-MODEL = #<NON-LINEAR-MAPPED-REGULAR-GRID-TERRAIN-MODEL @ #x2059e39a> CURVE-FN = #<Closure (:INTERNAL (METHOD INTERSECT-CAMERA-RAY-WITH-TERRAIN-MODEL ...))> S0 = 1.0 SEMI-INFINITE-P = T SYSTEM-TOOL::START = T EXCL::|local-0| = ... EXCL::|local-1| = ... EXCL::|local-2| = ... ... I tried (debug 3), but that didn't appear to help. Is this because the symbol names are not available, or because the debugger cannot figure out the assiciation between the stack locations and the local variables? In CMUCL with (declaim (optimize (safety 3)(space 1)(speed 2)(debug 9/4))) I find that most local variable values print as :<NOT-AVAILABLE> in the SLIME debugger. The debugger prints something like: 10: ((METHOD CME::INTERSECT-CURVE-WITH-DTM ...) Locals: PCL::.KEY. = :<NOT-AVAILABLE> PCL::.PV-CELL. = (#(1 2) . #()) PCL::.PV. = :<NOT-AVAILABLE> PCL::.REST-ARG. = (:SEMI-INFINITE-P T) PCL::.SLOTS0. = :<NOT-AVAILABLE> CURVE-FN = #<Closure Over Function "DEFMETHOD INTERSECT-CAMERA-RAY-WITH-TERRAIN-MODEL ...> DEFAULT-Z = :<NOT-AVAILABLE> DTM-TO-LVCS-TRANSFORM = :<NOT-AVAILABLE> FUNCTION = :<NOT-AVAILABLE> I tried: (declaim (optimize (safety 3)(space 0)(speed 0)(debug 3))), but that didn't appear to help. What is the problem?

2 1

[slime-devel] supported platforms
by Alex Mizrahi 22 Nov '04

22 Nov '04

Hello, All! looks like statement: -- SLIME works with .. and with XEmacs version 21 on Unix, OSX, and Win32. -- is incorrect. i have XEmacs 21.1.3 on Solaris x86 10 (because i found no newer binaries for this OS, and don't have C compiler to build new xemacs) and it refuses to work. it demanded lots of elisp files, after i copied them from newer xemacs (21.4.13) is said -- Symbol's chain of function indirections contains a loop: define-minor-mode -- which i don't know how to deal with.. so looks like slime is not working on XEmacs 21.1.3 or i'm missing something (possibly somewhere there is a set of elisp files which makes it work.. i tried latest of 21.1 - 21.1.14, it still doesn't work..) With best regards, Alex 'killer_storm' Mizrahi.

2 2

Re: [slime-devel] Re: sbcl regression with slime
by Helmut Eller 21 Nov '04

21 Nov '04

Christophe Rhodes <csr21(a)cam.ac.uk> writes: > I see this as an interim step towards what I would consider a proper > solution: the variant of (1) which reads "the communication protocol > between slime and lisp is defined over octets; where these octets are > to be interpreted as forming character data, the encoding is > ucs-4-bigendian". The point of this would be to allow those lisps > supporting more characters than 256 to communicate these characters, > while having those with just 256 (or fewer) characters simply deal > with a slightly more space-wasteful protocol. Why do you want to use ucs-4? Why not utf-8? Is that SBCL's internal format? If we want to use a multibyte encoding at all, we should also consider emacs-mule, that's Emacs' internal encoding used for multibyte characters. In general, I don't like this multibyte character shit. It seems to me like a feature that 99% of the users don't need. I certainly don't need it. Helmut.

4 11

[slime-devel] accept-connection
by Marco Baringer 21 Nov '04

21 Nov '04

is there any reason accept-connection's external-format argument doesn't default to :iso-latin-1-unix? -- -Marco Ring the bells that still can ring. Forget your perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen

2 1

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 20 Nov '04

20 Nov '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.572 slime/ChangeLog:1.575 --- slime/ChangeLog:1.572 Fri Nov 19 20:11:41 2004 +++ slime/ChangeLog Sat Nov 20 21:49:09 2004 @@ -1,3 +1,17 @@ +2004-11-20 Helmut Eller <heller(a)common-lisp.net> + + * swank-sbcl.lisp (make-socket-io-stream): Add some #+sb-unicode. + +2004-11-20 Travis Cross <travis(a)crosswirecorp.com> + + * swank-sbcl.lisp (thread-status): Fix unbalanced parenthesis. + +2004-11-20 Marco Baringer <mb(a)bese.it> + + * swank-openmcl.lisp (make-stream-interactive): Only add ouptut + streams (subclasses of ccl:fundamental-output-stream) to + ccl::*auto-flush-streams*. + 2004-11-19 Helmut Eller <heller(a)common-lisp.net> * slime.el (slime-net-coding-system): New variable. Specifies the

1 0

[slime-devel] [PATCH] (minor bug?)
by Travis Cross 20 Nov '04

20 Nov '04

When compiling SLIME (latest cvs) for SBCL 0.8.15, swank-sbcl.lisp would break with an 'unbalanced parenthesis' error. This patch fixed the issue for me (indentation was already correct). Thanks, -- Travis *** swank-sbcl.lisp.orig Fri Nov 19 14:06:36 2004 --- swank-sbcl.lisp Sat Nov 20 14:17:05 2004 *************** *** 856,862 **** (2 "stopped") (3 "dead") (t (format nil "??? ~A" state))))) ! (t "??? ???")))))) (defimplementation make-lock (&key name) (sb-thread:make-mutex :name name)) --- 856,862 ---- (2 "stopped") (3 "dead") (t (format nil "??? ~A" state))))) ! (t "??? ???"))))) (defimplementation make-lock (&key name) (sb-thread:make-mutex :name name))

2 1