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

[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] [patch] closing connections with :fd-handler style
by Stephen Compall 15 Mar '06

15 Mar '06

As far as I can tell, the only way a Swank connection object with style :fd-handler will ever be closed due to EOF (with close-connection) is if either the fd-handler implementation detects the EOF state and knows how to destroy Swank connections, or a condition is raised in the dynamic context of with-reader-error-handler. Looking at the topmost form in that context, however, it can only happen if (listen socket) answers T, so that the attempt to read can proceed and raise an eof-error, which gets wrapped up, etc. I modified process-available-input to test (listen socket) only after calling FN at least once; after all, it always returns T when the handler is called for a normal input state. Without this patch, my fd-handler backend gets into an endless loop calling the handler in install-fd-handler (with the :eof state); with this patch, the socket is closed, removed from *connections*, and from the fd-handler backend properly. Attached is the patch. -- Stephen Compall http://scompall.nocandysoftware.com/blog

2 4

[slime-devel] comma shortcut doesn't work always
by Edi Weitz 31 Jan '06

31 Jan '06

Another minor glitch that I encountered is that the comma shortcut in the REPL doesn't always work. I can consistently reproduce it (GNU Emacs 21.3.50 and also 21.3 release) like this: 1. Make sure point is at the beginning of a REPL input line. 2. Split Emacs frame into two windows, one of them being the REPL the other one containing something else. 3. Hide REPL window with C-x 0. 4. Now type M-x slime. 5. Type the comma. At this point I'm not asked for a shortcut command in the minibuffer but the comma is simply entered into the REPL instead. Anybody else seeing this? Cheers, Edi.

10 25

Re: [slime-devel] Re: CLISP SLIME implementation breaks in CVS
by Bill_Clementson＠peoplesoft.com 21 Jan '06

21 Jan '06

Luke Gorrie <luke(a)bluetail.com> writes: > Bill_Clementson(a)peoplesoft.com writes: > > > My previous SLIME installation was a CVS install from 4/18. I've just taken > > the latest CVS install and the CLISP SLIME implementation (under Windows) > > breaks. Here is the error: > > > > COERCE: #<MACRO #<COMPILED-CLOSURE SWANK::DEFSLIMEFUN>> cannot be coerced > > to type FUNCTION > > [Condition of type SIMPLE-TYPE-ERROR] > > I can reproduce this but I've no idea what is causing it. It /looks/ > like someone is trying to call defslimefun as a function rather than a > macro, but I don't see where it could happen -- the macro is declared > at the top of the only file that refers to it. > > I did fix a different but similar problem that I got under CLISP. It > seems like I had to swap the order of a couple of macros, one of which > expanded into into code that calls the other, but that surely can't be > the reason. > > > Backtrace: > > 0: EVAL frame for form (SWANK:CREATE-SWANK-SERVER 4007) > > Mine actually gives an empty backtrace (!). I fixed the Elisp-side to > handle that incase it helps someone more CLISP-savvy find the problem. Has anybody had any luck in finding the source of this problem? CLISP still breaks for me in the latest CVS. I have had a look at all of the DEFSLIMEFUN's that were modified since 4/18 (the previous CVS version that I had which was working ok with CLISP) and haven't found any obvious clues. Any suggestions on how I might debug this issue as it occurs at startup during the slime-connect processing in Emacs (after CLISP has started up successfully)? - Bill

5 6

[slime-devel] Installing slime for clisp 2.35 - Error
by Surendra Singhi 10 Jan '06

10 Jan '06

Hello, I recently upgraded to clisp 2.35 and now when I try to start slime on a lisp file, slime gets stuck. The *inferior-lisp* buffer shows me the following restart. ** - Continuable Error INTERN("*DOCUMENTATION*"): #<PACKAGE SYSTEM> is locked If you continue (by typing 'continue'): Ignore the lock and proceed The following restarts are also available: SKIP :R1 skip (COMPILE-FILES-IF-NEEDED-SERIALLY #) STOP :R2 stop loading file C:\Program Files\XEmacs\xemacs-packages\lisp\slime-1.2.1\swank-loader.lisp ABORT :R3 ABORT Doing 'continue', doesn't starts the slime repl, nor does selecting any of the restarts help. But, the inferior lisp buffer shows a lisp prompt, which can be used. What should I do to get over this problem? The slime related contents of my init file are: (load-library "inf-lisp") (setq inferior-lisp-program "C:\\clisp-2.35\\clisp.exe -I -m 256mb") (add-hook 'inferior-lisp-mode-hook (lambda () (inferior-slime-mode t))) (require 'timer) (require 'slime) (slime-setup) Thanks. -- Surendra Singhi http://www.public.asu.edu/~sksinghi/index.html "All animals are equal, but some animals are more equal than others." - Orwell, Animal Farm, 1945

5 8

[slime-devel] Connection broken (sbcl 0.9.7 & slime-cvs)
by Evrim ULU 06 Jan '06

06 Jan '06

Hi, I'm new to lis[t,p] :) I'm looking for help with slime/sbcl. Slime says: Lisp connection closed unexpectedly; * ;; Connection to Emacs lost. ;; [ debugger invoked on a SIMPLE-ERROR in thread #<THREAD "control-thread" {9B9D269}>: #<SB-SYS:FD-STREAM for "a constant string" {9A593C9}> is closed. debugger invoked on a SIMPLE-ERROR in thread #<THREAD "auto-flush-thread" {9B92CA1}>: #<SB-SYS:FD-STREAM for "a constant string" {9A593C9}> is closed. when i try to compile and load my lisp examples file (see attachments). I've seen a similar bug with cmucl on the list but i'm not sure if it is the same. It was about long files, this file is 307 lines long. I'm using slime-cvs along with emacs 22.0.50.1 on linux with nptl-only glibc. thnx in advance. evrim. (in-package :cl-user) (defun fun (x) (list 3 (expt (car x) 2))) (defmacro nil! (var) (list 'setq var nil)) (defun longer-than (x y) (> (length x) (length y))) (defun addlength (x) (cons (length x) x)) ;;(defun crank-call (caller callee) ;; '(hello callee this is caller calling)) (defun double (n) (* n 2)) (defun quad (n) (double (double n))) (defun stooge (larry moe curly) (list larry (list moe curly) curly 'larry)) (defun ms (x) (list (second x) (first x))) (defun if-test (x) (if (symbolp x) (list '(what the fuck?)) (list '(fuck the world!)))) (defun cond-test (x) (cond ((> x 0) x) ((< x 0) (- x)))) (defun variable-scope-test (x) (setf x (+ x 2))) (defun intersect2 (x y) (intersection x y)) (defun union2 (x y) (union x y)) (defun diff2 (x y) (set-difference x y)) (defun export_list () (setf *assoc-list1* '((key1 . val1) (key2 . val2) (key3 . val3)))) (defun assoc1 (x) (cdr (assoc x *assoc-list1*))) (defun rassoc1 (x) (car (rassoc x *assoc-list1*))) (defun export_list2 () (setf *list2* '((key1 valX val10 val11) (key2 valX val20 val21)))) (defun set-xor (x y) (set-exclusive-or (rest (assoc x *list2*)) (rest (assoc y *list2*)))) ;;; (remove-dups '(a a b c)) (defun remove-dups (x) (remove-duplicates x)) (defun substt (F G) (let ((y '(a b c))) (subst G F y))) (defun let-test (x y) (let ((a 1) (b 2)) (+ a b x y))) ;;; CL-USER> (subliss '(A . X) '(B . Y)) ;;; (X Y C) (defun subliss (F G) (let ((y '(A B C)) (final-list (cons F (list G))) ) ;; (sublis '((A . X) (B . Y) (C . Z)) y))) (sublis final-list y))) ;; (listp final-list))) ;;;· EQ is the fastest equality test: It compares addresses. Experts use ;;;it to compare symbols quickly, and to test whether two cons cells ;;;are physically the same object. It should not be used to compare ;;;numbers. ;;;· EQL is like EQ except it can safely compare numbers of the same ;;;type, such as two integers or two floating point numbers. It is the ;;;default equality test in Common Lisp. ;;;· EQUAL is the predicate beginners should use. It compares lists ;;;element by element; otherwise it works like EQL. ;;;· EQUALP is more liberal than EQUAL: It ignores case distinctions ;;;in strings, among other things. ;;;· = is the most efficient way to compare numbers, and the only way ;;;to compare numbers of disparate types, such as 3 and 3.0. It only ;;;accepts numbers. (defun member-equal (x) (let ((l '((3 kupa) (5 karo) (as maca)))) (member x l :test #'equal))) (defun remove-equal (x) (let ((l '((3 kupa) (5 karo) (as maca)))) (remove x l :test #'equal))) (defun squ (x) (* x x)) ;; (mapcar-test #'squ) ;; (1 4 9) (defun mapcar-test (x) (let ((y '(1 2 3))) (mapcar x y))) (defun mapcar-test2 () (mapcar #'(lambda (n) (* n n)) '(1 2 3))) ;; also, (setf fn #'cons) etc. ;; CL-USER> (my-assoc 'A) ;; (A 1) (defun my-assoc (key) (let ((y '((A 1) (B 2) (C 3)))) (find-if #'(lambda (entry) (equal key (first entry))) y))) ;;CL-USER> (my-assoc-remove-if 'A) ;;((B 2) (C 3)) ;; see also remove-if-not (defun my-assoc-remove-if (key) (let ((y '((A 1) (B 2) (C 3)))) (remove-if #'(lambda (entry) (equal key (first entry))) y))) ;; CL-USER> (reducee) ;; 6 (defun reducee () (let ((y '(1 2 3))) (reduce #'+ y))) ;; CL-USER> (everyy) ;; T (defun everyy () (let ((y '(1 2 3 4 5))) (every #'numberp y))) ;; CL-USER> (everyyy) ;; NIL ;; also, (every #'> '(10 20 30 40) '(1 2 3 4)) (defun everyyy () (let ((y '(1 2 3 4 5))) (every #'oddp y))) ;; (trace everyyy), (untrace everyyy) ;; CL-USER> (map-car2) ;; (11 22 33) (defun map-car2 () (let ((y '(1 2 3)) (x '(10 20 30))) (mapcar #'+ y x))) ;; (setf pred (make-greater-than-predicate 3)) ;; (funcall pred 2) => nil ;; (funcall pred 4) => t (defun make-greater-than-predicate (n) #'(lambda (x) (> x n))) ;; RECURSION ;; compares first if its odd, returns. ;; double-test tail recursion (defun anyoddp (x) (cond ((null x) nil) ((oddp (first x)) t) (t (anyoddp (rest x))))) ;; augmented tail recursion ;; means accumulation of recursive data ;; CL-USER> (count-slices '(A B C)) ;; 3 (defun count-slices (x) (cond ((null x) 0) (t (+ 1 (count-slices (rest x)))))) ;; list-consing recursion ;; constructs(cons) list every time (defun laugh (n) (cond ((zerop n) nil) (t (cons ’ha (laugh (- n 1)))))) ;; binary tree gezelim ;; CL-USER> (atoms-to-q '(A B (C D (E)))) ;; (Q Q (Q Q (Q))) (defun atoms-to-q (x) (cond ((null x) nil) ((atom x) 'q) (t (cons (atoms-to-q (car x)) (atoms-to-q (cdr x)))))) ;; loop-infinitely for (rest equals nil) (defun any-7-p (x) (cond ((equal (first x) 7) t) (t (any-7-p (rest x))))) (defun flattenn (x result) (cond ((null x) nil) ((atom x) (list x)) (t (append (flattenn (car x) result) (flattenn (cdr x) result))))) ;; INPUT/OUTPUT (defun 0utput () (progn (format t "xxx newline~&this is newline") (format t "this is a S-exp: ~S" 'cemisgezek))) ;; > (test "Hi, mom") ;; With escape characters: "Hi, mom" ;; Without escape characters: Hi, mom ;; NIL (defun 0utput2 (x) (format t "~&With escape characters: ~S" x) (format t "~&Without escape characters: ~A" x)) (defun draw-line () (format t "~&---------------------")) (defun draw-three (x) (format t "~& ~A | ~A | ~A~%" (filter (first x)) (filter (second x)) (filter (third x)))) (defun filter (x) (cond ((equal x nil) " ") (t x))) (defun draw-three2 (x) (format t "~& ~A | ~A | ~A~%" (first (filter2 x)) (second (filter2 x)) (filter2 (third x)))) (defun filter2 (x) (sublis '((nil . "")) x)) ;; CL-USER> (draw-board '(X 0 NIL X 0 NIL X 0 NIL)) ;; X | 0 | ;;--------------------- ;; X | 0 | ;;--------------------- ;; X | 0 | (defun draw-board (x) (draw-three2 x) (draw-line) (draw-three (nthcdr 3 x)) (draw-line) (draw-three (nthcdr 6 x))) ;; read input (defun what-da () (format t "~&enter number:") (let ((x (read))) (format t "~&entered: ~A" x))) (defun hashh() (let ((gee (make-hash-table))) ; (setf gee (make-hash-table)) (setf (gethash 'evrim gee) "i am your worst nightmare!") (format t "HASH VALUE: ~A~%" (gethash 'evrim gee)) (describe gee))) (defmacro simple-incf (var) (list 'setq var (list '+ var 1))) (defmacro set-zero (&rest variables) `(progn ,@(mapcar #'(lambda (var) (list 'setf var 0)) variables) '(zeroed ,@variables))) ;; DECLARE special ;; (setf x 2) ;; declaretest => 2 (defun declaretest () (let ((x 1)) (locally (declare (special x)) x)))

2 2

[slime-devel] Daily ChangeLog diff
by lgorrie＠common-lisp.net 31 Dec '05

31 Dec '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.825 slime/ChangeLog:1.826 --- slime/ChangeLog:1.825 Tue Dec 27 16:14:44 2005 +++ slime/ChangeLog Sat Dec 31 16:08:22 2005 @@ -1,3 +1,8 @@ +2005-12-31 Harald Hanche-Olsen <hanche(a)math.ntnu.no> + + * slime.el (slime-open-stream-to-lisp): Inherit the + process-coding-system from the current connection. + 2005-12-27 Helmut Eller <heller(a)common-lisp.net> Keep a history of protocol events for better bug reports.

1 0

[slime-devel] Coding systems: suggested change to slime-open-stream-to-lisp
by Harald Hanche-Olsen 31 Dec '05

31 Dec '05

May I suggest the following patch to slime-open-stream-to-lisp: --- slime.el 30 Dec 2005 19:26:22 +0100 1.574 +++ slime.el 30 Dec 2005 22:58:49 +0100 @@ -2775,9 +2775,8 @@ (list* '("<" . slime-mark-presentation-start-handler) '(">" . slime-mark-presentation-end-handler) bridge-handlers))) - (set-process-coding-system stream - slime-net-coding-system - slime-net-coding-system) + (let ((pcs (process-coding-system (slime-current-connection)))) + (set-process-coding-system stream (car pcs) (cdr pcs))) (when-let (secret (slime-secret)) (slime-net-send secret stream)) stream)) It appears to solve the following problem. I have not changed slime-net-coding-system from its default value, but I have (setf slime-lisp-implementations '((sbcl ("sbcl") :coding-system utf-8-unix) (cmucl ("cmucl") :coding-system iso-latin-1-unix))) So when I run sbcl, coding systems on the emacs and sbcl sides match for input and printing of values, but there is a mismatch on printing from lisp code: The sbcl side uses utf-8, while the emacs side assumes latin-1. Quick demo (first good, second bad): cl-user> #\å #\å cl-user> (format t "~C" #\å) Ã¥ nil - Harald

2 1

[slime-devel] Re: Putting REPL prompt on the mode line?
by bdowning＠lavos.net 30 Dec '05

30 Dec '05

On Wed, Dec 21, 2005 at 07:54:10PM -0800, Derek Peschel wrote: > >More importantly to me, the prompt tells me "this is what *PACKAGE* was > >when I ran this command n {minutes,hours,days} ago." I'd be very > >unhappy for that information to go away. > > I wodnered if that issue would come up. If the information was stored > as a property of the text region that contains the command, and displayed > on the mode line or something, would that work for you? My gut feeling is that putting more distance between the expression and the package it was run in is not a win for me. Plus you'd have to put point on it to determine it that way which is quite inconvenient. > Do you want to see that kind of prompt in an editor buffer or let the > editor take care of it? In a normal Lisp buffer I agree - its primary purpose is editing the file, and interaction with the Lisp is secondary. Having a buffer-package shown on the mode-line works well in that case. However, I think the REPL buffer is a different story - interaction is primary there, so I think the prompt works well (for me). > I'm going a step further and changing the way the package and evaluation > state are shown. It's purely for appearance. Would a REPL buffer be nicer > if the left margins of all lines of input and output were aligned? IMHO, no. I like having the input indented by the prompt because it helps delimit what exactly is input without relying on font faces. Please experiment, though. Just make the end product be a customize option and everyone will be happy. :-) -bcd

3 2

[slime-devel] XEmacs-nomule, slime cvs 20051202, sbcl 0.9.7
by Adam Fabian 30 Dec '05

30 Dec '05

Hi. I'm having trouble with the above configuration. I saw this thread: http://article.gmane.org/gmane.lisp.slime.devel/4367 http://article.gmane.org/gmane.lisp.slime.devel/4368 that looks like it might be the same or a related problem. I'm not really sure. Looked around the mailing list, did some web searching, I don't think this is a duplicate report. Anyway, if I try to M-x slime with XEmacs-nomule (which is what I normally use) I get: Invalid slime-net-coding-system: nil. (iso-latin-1-unix iso-8859-1-unix bina (cuts off, I don't know how to read more of the minibuffer) as an error. If I try the mule version, which my distribution packages, I get a segmentation fault from XEmacs (this, of course, is probably better reported as an XEmacs bug, which I'm planning on doing.) This is XEmacs 21.4.17 with slime cvs 20051202 and sbcl 0.9.7. This is my first time trying to start things up. (That is to say, I had no working previous configuration.) I really don't know what to make of this, but here's what I get if I try it after setting debug-on-error to t: Debugger entered--Lisp error: (error "Invalid slime-net-coding-system: nil. (iso-latin-1-unix iso-8859-1-unix binary utf-8-unix emacs-mule-unix euc-jp-unix)") signal(error ("Invalid slime-net-coding-system: nil. (iso-latin-1-unix iso-8859-1-unix binary utf-8-unix emacs-mule-unix euc-jp-unix)")) cerror("Invalid slime-net-coding-system: %s. %s" nil (iso-latin-1-unix iso-8859-1-unix binary utf-8-unix emacs-mule-unix euc-jp-unix)) apply(cerror "Invalid slime-net-coding-system: %s. %s" (nil (iso-latin-1-unix iso-8859-1-unix binary utf-8-unix emacs-mule-unix euc-jp-unix))) error("Invalid slime-net-coding-system: %s. %s" nil (iso-latin-1-unix iso-8859-1-unix binary utf-8-unix emacs-mule-unix euc-jp-unix)) (if props nil (error "Invalid slime-net-coding-system: %s. %s" coding-system (mapcar ... slime-net-valid-coding-systems))) (unless props (error "Invalid slime-net-coding-system: %s. %s" coding-system (mapcar ... slime-net-valid-coding-systems))) (let ((props ...)) (unless props (error "Invalid slime-net-coding-system: %s. %s" coding-system ...)) (when (and ... ...) (assert default-enable-multibyte-characters)) t) slime-check-coding-system(nil) (let ((args ...)) (slime-check-coding-system coding-system) (when (or ... ...) (let ... ... ...))) (catch (quote --cl-block-slime-start--) (let (...) (slime-check-coding-system coding-system) (when ... ...))) (cl-block-wrapper (catch (quote --cl-block-slime-start--) (let ... ... ...))) (block slime-start (let (...) (slime-check-coding-system coding-system) (when ... ...))) (let* ((program ...) (program-args ...) (coding-system ...) (init ...) (name ...) (buffer ...)) (let (...) (while --keys--102022 ...)) (block slime-start (let ... ... ...))) slime-start(:program "/usr/local/bin/sbcl" :program-args nil) apply(slime-start (:program "/usr/local/bin/sbcl" :program-args nil)) (lambda (&optional command coding-system) "Start an inferior^_superior Lisp and connect to its Swank server." (interactive) (apply (function slime-start) (slime-read-interactive-args)))() call-interactively(slime) command-execute(slime t) execute-extended-command(nil) call-interactively(execute-extended-command)

3 2

[slime-devel] Problems with lambda-gtk + slime on windows/clisp
by Ignas Mikalajunas 28 Dec '05

28 Dec '05

Hi, what can i do to avoid emacs/slime freezing when running simple GTK examples on clisp ? I can run hello-world on a stand-alone clisp, yet whenever i am evaluating the function in emacs - slime just stops responding ... (no errors can be seen anywhere). I have tried fiddling with communication styles, yet non except "nil" were accepted. Maybe anyone had simmilar problems with SDL/LTK/wxCL? Ignas Mikalajunas

2 2

[slime-devel] Daily ChangeLog diff
by lgorrie＠common-lisp.net 27 Dec '05

27 Dec '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.824 slime/ChangeLog:1.825 --- slime/ChangeLog:1.824 Thu Dec 22 17:06:49 2005 +++ slime/ChangeLog Tue Dec 27 16:14:44 2005 @@ -1,3 +1,13 @@ +2005-12-27 Helmut Eller <heller(a)common-lisp.net> + + Keep a history of protocol events for better bug reports. + + * swank.lisp (log-event): Record the event in the history buffer. + (*event-history*): Buffer for events. + (dump-event-history): New function. + (close-connection): Escape non-ascii strings and include the event + history in the error message. + 2005-12-22 Helmut Eller <heller(a)common-lisp.net> Make highlighting of modified text a minor mode. Also use

1 0

[slime-devel] Can't start slime (OS X 10.3, Slime 1.2.1, OpenMCL 1.0)
by Carl Tucker 27 Dec '05

27 Dec '05

Hi, I'm having a problem getting slime to work. I'm new to this, so I apologize if I'm doing something stupid. Here's what happens when I start emacs and type M-x slime I get a new buffer, called *inferior-lisp* which then outputs the following: (load "/Users/cfta/lisp/slime-1.2.1/swank-loader.lisp" :verbose t) (swank:start-server "/tmp/slime.2167" :external-format :iso-latin-1-uni x) Welcome to OpenMCL Version 1.0 (DarwinPPC32)! ? ;Loading #P"/Users/cfta/lisp/slime-1.2.1/swank-loader.lisp"... ;Loading #P"/Users/cfta/.slime/fasl/openmcl-1.0-darwin-powerpc/swank -backend.dfs\l"... ;Loading #P"/Users/cfta/.slime/fasl/openmcl-1.0-darwin-powerpc/nregex.dfsl"... ;Loading #P"/Users/cfta/.slime/fasl/openmcl-1.0-darwin-powerpc/metering.dfsl"... ;Compiling "/Users/cfta/lisp/slime-1.2.1/swank-openmcl.lisp"... ;Compiler warnings for "/Users/cfta/lisp/slime-1.2.1/swank-openmcl.lisp" : ; Unused lexical variable STREAM, in (MAKE-STREAM-INTERACTIVE (T)). ; Warning: Interface file #P"ccl:darwin-headers;libc;functions.cdb" does not exist. ; While executing: CCL::CDB-OPEN Read error between positions 8480 and 8595 in /Users/cfta/lisp/slime-1.2.1/ swank\-openmcl.lisp. > Error in process listener(1): Foreign function not found: DARWIN32::|tmpnam| > While executing: CCL::LOAD-EXTERNAL-FUNCTION > Type :POP to abort. Type :? for other options. 1 > then I'm stuck in the debugger. If I type :pop to abort, I'm able to use the inferior lisp buffer as a lisp interpreter. If I open a new buffer and try to write some code, the mode line says (Lisp Slime[Polling: XXX]) , where the polling number just counts up. Nothing ever happens. None of the compile macros work either- C-c C-c says "not connected." Is it a problem with the way I've set the system up? I tried to follow the instructions for installing Open MCL and Slime, but I'm not sure I completely understood what I was doing with either. Thanks.

2 2

[slime-devel] slime starting problems
by Peter Herth 24 Dec '05

24 Dec '05

Hi, I just tried to run newest cvs slime with sbcl 0.9.7 and aquamacs, and I am stuck with the error message: error in process filter: Wrong number of arguments: nil, 12 Anyone an idea whats the problem? Peter

1 1

[slime-devel] Daily ChangeLog diff
by lgorrie＠common-lisp.net 22 Dec '05

22 Dec '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.823 slime/ChangeLog:1.824 --- slime/ChangeLog:1.823 Tue Dec 20 01:25:58 2005 +++ slime/ChangeLog Thu Dec 22 17:06:49 2005 @@ -1,3 +1,15 @@ +2005-12-22 Helmut Eller <heller(a)common-lisp.net> + + Make highlighting of modified text a minor mode. Also use + after-change-functions instead of rebinding all self-inserting + keys. + + * slime.el (slime-highlight-edits-mode): New minor mode. + (slime-self-insert-command): Deleted. + (slime-before-compile-functions): New hook to decouple edit + highlighting from compilation. + (slime-highlight-edits-face): Renamed from slime-display-edit-face. + 2005-12-20 Marco Baringer <mb(a)bese.it> When inspecting classes, methods and generic functions show all

1 0

[slime-devel] Weird Display Bug w/ open minibuffer
by Stefan Kamphausen 22 Dec '05

22 Dec '05

Hi, I just came across a really weird display bug: 1. Start Slime 2. start CMUCL 3. open a lisp file and type something until you want to complete sth (in this case I wanted to complete #\New to #\Newline and it didn't work, but that's another story). Just make sure that there is only one possible completion. 4. Now do something to invoke a minibuffer dialog (say C-x C-f) 5. Go back to your lisp file w/o finishing the dialog (in Xemacs I can just C-x o out of the dialog). 6. Hit M-TAB for the completion The result is that the message "[Sole completion]" doesn't show up in the echo area but in the last line of the buffer. And it disappears a few seconds later. I tried to get the same thing with hippie-expand in a cperl-mode-buffer but there the message showed up in the echo area. So maybe it's in Slime. It may be an XEmacs problem, sure, and it's not really that important that it really needs a fix. Agreed. It's funny and weird nevertheless and I thought I'd let you know. Regards, Stefan PS: Slime: CVS of yesterday with Peter's Patch applied XEmacs: 21.4 (patch 17) "Jumbo Shrimp" XEmacs Lucid CMUCL: CMU Common Lisp CVS 19c 19c-release + minimal debian patches (19C) System: Gentoo Linux -- Telefonieren Sie schon oder sparen Sie noch? NEU: GMX Phone_Flat http://www.gmx.net/de/go/telefonie

1 0

[slime-devel] Symbol's function definition is void: syntax-ppss
by Chisheng Huang 22 Dec '05

22 Dec '05

The message on the Subject line is printed once in the mini buffer for every character entered into the REPL buffer. This is annoying and makes it impossible to type fast. Best, -cph

3 3

[slime-devel] Putting REPL prompt on the mode line?
by dpeschel＠eskimo.com 22 Dec '05

22 Dec '05

As a first step toward my general goal of making a LISP interface that is designed for random-access displays rather than simulated Teletypes, I thought I would get the prompt out of REPL buffers and put the same information on their mode lines. A one-line change to sline.el prevents printing the prompt string, but then I notice that "Evaluation aborted" messages appear in bold. Probably the face used for input that has been completed is being used for the messages. Is there any complete spec for what can appear in REPL buffers, so I know what code needs to be changed? The one-line change is to slime-repl-insert-prompt (line 2642 in SLIME 1.2.1): < (prompt (format "%s> " (slime-lisp-package-prompt-string)))) --- > (prompt "")) The next problem is to put the information in the mode line or perhaps in the top pane that currently shows the port and process IDs. The standard prompt shows the current package. To the user, the prompt also means "evaluation of the last form (or initialiation) was aborted or is complete" as well as "the reader is expecting new input and is not in the middle of reading anything". Does SLIME have a notion of package change, evaluation completion or abortion, and reader state change as separate events? Does the SWANK protocol allow them to be sent as signals that don't depend on any particular text output also being sent to SLIME at the same time? Thanks for your help, -- Derek

2 1

[slime-devel] Daily ChangeLog diff
by lgorrie＠common-lisp.net 20 Dec '05

20 Dec '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.821 slime/ChangeLog:1.823 --- slime/ChangeLog:1.821 Sun Dec 18 18:24:36 2005 +++ slime/ChangeLog Tue Dec 20 01:25:58 2005 @@ -1,3 +1,17 @@ +2005-12-20 Marco Baringer <mb(a)bese.it> + + When inspecting classes, methods and generic functions show all + the slots in the case that what we're inspecting is a subclass of + the standard class and has extra user defined slots. + + * swank.lisp (all-slots-for-inspector): New function. + (inspect-for-emacs): Use all-slots-for-inspector. + +2005-12-19 Peter Seibel <peter(a)gigamonkeys.com> + + * slime.el (slime-self-insert-command): Got rid of message about + setting up face and skipping edit-hilights when in a comment. + 2005-12-18 Nikodemus Siivola <nikodemus(a)random-state.net> * slime.el (slime-mode-hook): Bind simple characters to

1 0

[slime-devel] Re: net-read-error
by Aleksandar Bakic 20 Dec '05

20 Dec '05

Hi, > error in process filter: byte-code: net-read error: (end-of-file) > error in process filter: net-read error: (end-of-file) Please disregard the above. There was a change in slime-connect that confused me. I fixed the problem. Alex __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

[slime-devel] SLIME, CMUCL 19c, and Garnet
by C Y 20 Dec '05

20 Dec '05

Hi all. I tried building the CVS garnet inside of SLIME using 19c last night, and after a couple corrections the build seemed to proceed well until I got an exit from CMUCL with error of either 256 or 265 (naturally I forgot which.) My first guess is that I just ran out of memory - is there any way to increase CMUCL's settings related to this type of thing? Or do I just need more physical memory? (I only have 256 :-/) Alternately, if it's not memory what could cause something like this? I was able to build Garnet successfully from the command line. Has anybody else ever built Garnet inside SLIME? Cheers, CY __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

[slime-devel] C-u stops working is a lisp buffer after 2005-12-17
by Chisheng Huang 19 Dec '05

19 Dec '05

Hi, With Slime checked out from the CVS on and after 2005-12-17, the C-u command (universal-argument) stops working in a Lisp buffer. For example, if you type "C-u 6 a" in a Lisp buffer, you'll only get "a", instead of "aaaaaa". Could someone please fix it? Best wishes, -cph, an elisp idiot.

1 0

[slime-devel] net-read-error
by Aleksandar Bakic 19 Dec '05

19 Dec '05

Hi, I recently (and again, a few minutes ago) updated my slime and it started causing problems. Sometimes in the inspector, I get: error in process filter: byte-code: net-read error: (end-of-file) error in process filter: net-read error: (end-of-file) and slime disconnects: debugger invoked on a SIMPLE-ERROR in thread #<THREAD "auto-flush-thread" {ECA8811}>: #<SB-SYS:FD-STREAM for "a constant string" {EB93141}> is closed. ;; Connection to Emacs lost. ;; [end of file on #<SB-SYS:FD-STREAM for "a constant string" {ECB3801}>] My setup is: uname: Linux 2.6.9-1.667 #1 Tue Nov 2 14:50:10 EST 2004 x86_64 x86_64 x86_64 GNU/Linux SBCL: 0.9.6.52 I use utf-8 and also do (setq swank::*coding-system* :utf-8-unix) before creating the swank server. Thanks, Alex __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

Solved (sort of): Re: [slime-devel] Re: slime cvs 20051213, XEmacs 21.4.17
by Adam Fabian 19 Dec '05

19 Dec '05

On 12/15/05, James McIlree <ovrskeek(a)mac.com> wrote: > This is from an earlier email to slime-devel. Might > be the same bug? Worth a try, at least. ... > > This appears to be a compiler issue with gcc in 10.4, if you > > configure xemacs with: > > > > ./configure --cflags="-g" > > > > Slime will once again be able to connect. I compiled XEmacs 21.4.18, and everything seems to be working fine. I was using my distribution's (Ubuntu's) XEmacs 21.4.17, which is definitely stripped, if that makes a difference, though I don't quite understand why. I'll just use my compiled version without ever really grasping what the problem is or was. Just following up. Thanks for the tip. Adam

1 0