February 2006 - 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] Odd bug - heads up
by Alan Ruttenberg 15 Mar '06

15 Mar '06

I found that presentations which were in my repl input history, weren't being recalled as presentations when I recalled previous history - they were coming back as text, and so would generally trigger a reader error when I tried the command. I tracked this down to (defun slime-repl-replace-input (string) (slime-repl-delete-current-input) (setq it string) (insert-and-inherit string)) If one uses insert, instead of insert-and-inherit then repl history works correctly for presentations, for me. No idea why this is problematic. It looks like this function has been this way for a long time - perhaps a bug in the emacs I am using (OS X tiger, fink installed, I think). Anyways, thought I'd post this in case anyone else was having the same problem, or had some insight as to why this is happening. -Alan

2 1

[slime-devel] SLIME+Allegro on Windows
by mikel 06 Mar '06

06 Mar '06

Franz wants Peter Seibel's Lispbox to work with acl on Windows. The obstacle is that acl is not a console application on Windows, and doesn't provide a connection to standard input and standard output in the normal way. I've agreed to do a little legwork to find a way around this problem, and the first thing it occurred to me to do was to ask SLIME-devel what sort of connection support SLIME would need to connect to acl. Is it sufficient for the running acl to provide sockets, so that the lisp-side server can respond to the emacs-side SLIME protocol? What issues am I not thinking of in my naive view of this problem?

10 11

[slime-devel] News from the stepper ?
by Didier Verna 27 Feb '06

27 Feb '06

Hi ! I was wondering about the status of the slime stepper: I've seen one or two posts about it on this list, but it was like 17 weeks ago. So is it still an active project ? Is it usable ? Thanks a lot. -- Didier Verna, didier(a)lrde.epita.fr, http://www.lrde.epita.fr/~didier EPITA / LRDE, 14-16 rue Voltaire Tel.+33 (1) 44 08 01 85 94276 Le Kremlin-Bicêtre, France Fax.+33 (1) 53 14 59 22 didier(a)xemacs.org

1 0

[slime-devel] Minor problem
by Antonio Menezes Leitao 26 Feb '06

26 Feb '06

Hi, I would like to report a small problem in Slime. Here is the scenario: 1. On a lisp file, change one definition and slime-compile-defun it (C-c C-c). 2. Save the changed buffer. 3. Kill the saved buffer. 4. slime-edit-definition for the changed definition. 5. Emacs complains that it is trying to set-buffer on a non-existent buffer. This occurs with, at least, SBCL, CMUCL, and Allegro. As far as I can see, the problem is that the implementation of swank-compile-string (which is used by slime-compile-defun) ignores the buffer's filename-directory and this makes it impossible for emacs to recover the correct file. I agree that when we are using a buffer that is not connected to a file, that's the proper behavior. However, IMHO, that's not a frequent situation. To solve this problem for Allegro, I made the following quick (and ugly) hack in swank-allegro.lisp: (defimplementation swank-compile-string (string &key buffer position directory) ;; We store the source buffer in excl::*source-pathname* as a string ;; of the form <buffername>;<start-offset>. Quite ugly encoding, but ;; the fasl file is corrupted if we use some other datatype. (with-compilation-hooks () (let ((*buffer-name* buffer) (*buffer-start-position* position) (*buffer-string* string) (*default-pathname-defaults* (if directory (merge-pathnames (pathname directory)) *default-pathname-defaults*))) (compile-from-temp-file (format nil "~S ~S~%~A" `(in-package ,(package-name *package*)) `(eval-when (:compile-toplevel :load-toplevel) (setq excl::*source-pathname* ,(format nil "~A~A;~D" (or directory "") buffer position))) string))))) Then, to recover the source pathname, I changed the following function: (defun find-definition-in-buffer (filename) (let ((directory-p (find #\/ filename :from-end t))) (let ((pos (position #\; filename :from-end t))) (multiple-value-bind (name position) (values (subseq filename 0 pos) (parse-integer (subseq filename (1+ pos)))) (make-location (if directory-p (list :file name) (list :buffer name)) (list :position position)))))) As I said before, it's not a pretty solution :-) Best regards, António Leitão.

1 0

[slime-devel] slime-macroexpand-in-place
by Marco Baringer 26 Feb '06

26 Feb '06

hi, the attached patch provides a function, slmie-macroexpand-in-place, which does exactly what slmie-macroexpand-1 does but replaces the text of the form with its expansion. i've found this very usefull in a *SLME Macroexpansion* buffer and i plan on commiting it. however i don't know what keys to bind it to. is there a way to create a minor-mode such that the slime-macroexpand-1-in-place and slime-macroexpand-all-in-place are bound to the same keys as what the user has bound slime-macroexpand-1 and slmie-macroexpand-all to? -- -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

4 5

[slime-devel] Unimplemented slime function and sbcl
by Jonathon McKitrick 25 Feb '06

25 Feb '06

Hi all, I'm just wondering... there are a handful of functions SLIME provides that are not implemented under sbcl. Is this going to happen anytime soon or at all? Several would be useful, but if sbcl ever implementes single-stepping, that feature would be invaluable. -Jonathon -- "I am sure that Jesus would use a command prompt. Hello? Ten Commandments??"

1 0

[slime-devel] *slime-repl nil*
by Austin Haas 25 Feb '06

25 Feb '06

When starting slime (latest from CVS), the repl buffer is being shown with name: *slime-repl nil* It's also showing: ; Adding fd handler: 5 at the end of the *inferior-lisp* buffer, and: ; Adding fd handler: 6 CL-USER> CL-USER> at the start of the repl. I am using SBCL 0.9.9 on a Xen server. Is this a sign of a problem? I'm having trouble running a tbnl application (which runs fine on my local server) and this seemed to be the first clue towards something unusual. Thanks. -austin

1 1

Re: [slime-devel] SLIME+Allegro on Windows
by Edi Weitz 25 Feb '06

25 Feb '06

On Thu, 23 Feb 2006 14:47:20 -0800, mikel evins <mevins(a)mac.com> wrote: > Thanks very much, Edi. I'll start with this. Bill Clementson reminded me that I forgot to post the contents of my ~/.slime.lisp file, so here it is: (load "c:/emacs/site-lisp/slime/swank-loader.lisp") #-clisp (swank::create-swank-server 4005 :spawn #'swank::simple-announce-function t) #+clisp (swank::create-swank-server 4005) The first line loads the stock swank-loader.lisp from SLIME. Thanks Bill... :)

2 1

Re: [slime-devel] SLIME+Allegro on Windows
by Bill Clementson 23 Feb '06

23 Feb '06

Hi Edi, > (start-lisp-and-wait "c:/PROGRA~1/acl80/alisp.exe +B +cm -L ~/.slime.lisp&")) You neglected to mention the contents of the .slime.lisp file. It should contain at least the following 2 lines: (load "/path/to/slime/swank-loader.lisp") (swank::create-swank-server 4005) Cheers, Bill

1 0

[slime-devel] swank-ecl & compile-from-stream
by Tomi Neste 18 Feb '06

18 Feb '06

Compile-from-stream in swank-ecl.lisp seems to generate and compile empty files which can be a bit confusing, the attached patch should fix that. T. Neste

1 0

[slime-devel] SLIME halt at loading occasionally CLISP + WinXP
by Quest NeoX 18 Feb '06

18 Feb '06

1 0

[slime-devel] SLIME stop working in CLisp + WinXP the second run
by Quest NeoX 18 Feb '06

18 Feb '06

1 0

[slime-devel] OK to install this SBCL pretty printer patch into SLIME CVS?
by Matthias Koeppe 17 Feb '06

17 Feb '06

Hi, I would like to install a new file, "sbcl-pprint-patch.lisp", into SLIME CVS. It patches the SBCL pretty printer, so as to support printing SLIME presentations through a pretty printing stream. The file will only be loaded when a user loads the SLIME file "present.lisp". A set of equivalent changes to the pretty printer have been included in CMUCL 19c. I have also tried to get the patch into SBCL, but it seems the maintainers are not interested in merging it. Any objections to installing it into SLIME CVS? Matthias Index: present.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/present.lisp,v retrieving revision 1.17 diff -u -p -u -r1.17 present.lisp --- present.lisp 21 Sep 2005 20:33:46 -0000 1.17 +++ present.lisp 6 Feb 2006 19:25:17 -0000 @@ -68,8 +68,12 @@ don't want to present anything" ;; layout. (slime-stream-p (pretty-print::pretty-stream-target stream)))) #+sbcl - (and (typep stream 'sb-impl::indenting-stream) - (slime-stream-p (sb-impl::indenting-stream-stream stream))) + (or (and (typep stream 'sb-impl::indenting-stream) + (slime-stream-p (sb-impl::indenting-stream-stream stream))) + (and (typep stream 'sb-pretty::pretty-stream) + (fboundp 'sb-pretty::enqueue-annotation) + (not *use-dedicated-output-stream*) + (slime-stream-p (sb-pretty::pretty-stream-target stream)))) #+allegro (and (typep stream 'excl:xp-simple-stream) (slime-stream-p (excl::stream-output-handle stream))) @@ -83,6 +87,17 @@ don't want to present anything" (declare (ignore stream)) *enable-presenting-readable-objects*) +;;; Get pretty printer patches for SBCL +#+sbcl +(eval-when (:compile-toplevel :load-toplevel :execute) + (handler-bind ((simple-error + (lambda (c) + (declare (ignore c)) + (let ((clobber-it (find-restart 'sb-kernel::clobber-it))) + (when clobber-it (invoke-restart clobber-it)))))) + (sb-ext:without-package-locks + (swank-backend::with-debootstrapping (load "sbcl-pprint-patch.lisp"))))) + ;; If we are printing to an XP (pretty printing) stream, printing the ;; escape sequences directly would mess up the layout because column ;; counting is disturbed. Use "annotations" instead. @@ -97,7 +112,12 @@ don't want to present anything" (fboundp 'pp::enqueue-annotation)) (pp::enqueue-annotation stream function arg) (funcall function arg stream nil))) -#-(or allegro cmu) +#+sbcl +(defun write-annotation (stream function arg) + (if (typep stream 'sb-pretty::pretty-stream) + (sb-pretty::enqueue-annotation stream function arg) + (funcall function arg stream nil))) +#-(or allegro cmu sbcl) (defun write-annotation (stream function arg) (funcall function arg stream nil)) *** /dev/null Sun Jan 1 08:47:07 2006 --- sbcl-pprint-patch.lisp Sun Jul 24 04:19:06 2005 *************** *** 0 **** --- 1,324 ---- + (in-package "SB!PRETTY") + + (defstruct (annotation (:include queued-op)) + (handler (constantly nil) :type function) + (record)) + + + (defstruct (pretty-stream (:include sb!kernel:ansi-stream + (out #'pretty-out) + (sout #'pretty-sout) + (misc #'pretty-misc)) + (:constructor make-pretty-stream (target)) + (:copier nil)) + ;; Where the output is going to finally go. + (target (missing-arg) :type stream) + ;; Line length we should format to. Cached here so we don't have to keep + ;; extracting it from the target stream. + (line-length (or *print-right-margin* + (sb!impl::line-length target) + default-line-length) + :type column) + ;; A simple string holding all the text that has been output but not yet + ;; printed. + (buffer (make-string initial-buffer-size) :type (simple-array character (*))) + ;; The index into BUFFER where more text should be put. + (buffer-fill-pointer 0 :type index) + ;; Whenever we output stuff from the buffer, we shift the remaining noise + ;; over. This makes it difficult to keep references to locations in + ;; the buffer. Therefore, we have to keep track of the total amount of + ;; stuff that has been shifted out of the buffer. + (buffer-offset 0 :type posn) + ;; The column the first character in the buffer will appear in. Normally + ;; zero, but if we end up with a very long line with no breaks in it we + ;; might have to output part of it. Then this will no longer be zero. + (buffer-start-column (or (sb!impl::charpos target) 0) :type column) + ;; The line number we are currently on. Used for *PRINT-LINES* + ;; abbreviations and to tell when sections have been split across + ;; multiple lines. + (line-number 0 :type index) + ;; the value of *PRINT-LINES* captured at object creation time. We + ;; use this, instead of the dynamic *PRINT-LINES*, to avoid + ;; weirdness like + ;; (let ((*print-lines* 50)) + ;; (pprint-logical-block .. + ;; (dotimes (i 10) + ;; (let ((*print-lines* 8)) + ;; (print (aref possiblybigthings i) prettystream))))) + ;; terminating the output of the entire logical blockafter 8 lines. + (print-lines *print-lines* :type (or index null) :read-only t) + ;; Stack of logical blocks in effect at the buffer start. + (blocks (list (make-logical-block)) :type list) + ;; Buffer holding the per-line prefix active at the buffer start. + ;; Indentation is included in this. The length of this is stored + ;; in the logical block stack. + (prefix (make-string initial-buffer-size) :type (simple-array character (*))) + ;; Buffer holding the total remaining suffix active at the buffer start. + ;; The characters are right-justified in the buffer to make it easier + ;; to output the buffer. The length is stored in the logical block + ;; stack. + (suffix (make-string initial-buffer-size) :type (simple-array character (*))) + ;; Queue of pending operations. When empty, HEAD=TAIL=NIL. Otherwise, + ;; TAIL holds the first (oldest) cons and HEAD holds the last (newest) + ;; cons. Adding things to the queue is basically (setf (cdr head) (list + ;; new)) and removing them is basically (pop tail) [except that care must + ;; be taken to handle the empty queue case correctly.] + (queue-tail nil :type list) + (queue-head nil :type list) + ;; Block-start queue entries in effect at the queue head. + (pending-blocks nil :type list) + ;; Queue of annotations to the buffer + (annotations-tail nil :type list) + (annotations-head nil :type list)) + + + (defmacro enqueue (stream type &rest args) + (let ((constructor (intern (concatenate 'string + "MAKE-" + (symbol-name type)) + "SB-PRETTY"))) + (once-only ((stream stream) + (entry `(,constructor :posn + (index-posn + (pretty-stream-buffer-fill-pointer + ,stream) + ,stream) + ,@args)) + (op `(list ,entry)) + (head `(pretty-stream-queue-head ,stream))) + `(progn + (if ,head + (setf (cdr ,head) ,op) + (setf (pretty-stream-queue-tail ,stream) ,op)) + (setf (pretty-stream-queue-head ,stream) ,op) + ,entry)))) + + ;;; + ;;; New helper functions + ;;; + + (defun enqueue-annotation (stream handler record) + (enqueue stream annotation :handler handler + :record record)) + + (defun re-enqueue-annotation (stream annotation) + (let* ((annotation-cons (list annotation)) + (head (pretty-stream-annotations-head stream))) + (if head + (setf (cdr head) annotation-cons) + (setf (pretty-stream-annotations-tail stream) annotation-cons)) + (setf (pretty-stream-annotations-head stream) annotation-cons) + nil)) + + (defun re-enqueue-annotations (stream end) + (loop for tail = (pretty-stream-queue-tail stream) then (cdr tail) + while (and tail (not (eql (car tail) end))) + when (annotation-p (car tail)) + do (re-enqueue-annotation stream (car tail)))) + + (defun dequeue-annotation (stream &key end-posn) + (let ((next-annotation (car (pretty-stream-annotations-tail stream)))) + (when next-annotation + (when (or (not end-posn) + (<= (annotation-posn next-annotation) end-posn)) + (pop (pretty-stream-annotations-tail stream)) + (unless (pretty-stream-annotations-tail stream) + (setf (pretty-stream-annotations-head stream) nil)) + next-annotation)))) + + (defun invoke-annotation (stream annotation truncatep) + (let ((target (pretty-stream-target stream))) + (funcall (annotation-handler annotation) + (annotation-record annotation) + target + truncatep))) + + (defun output-buffer-with-annotations (stream end) + (let ((target (pretty-stream-target stream)) + (buffer (pretty-stream-buffer stream)) + (end-posn (index-posn end stream)) + (start 0)) + (loop + for annotation = (dequeue-annotation stream :end-posn end-posn) + while annotation + do + (let ((annotation-index (posn-index (annotation-posn annotation) + stream))) + (when (> annotation-index start) + (write-string buffer target :start start + :end annotation-index) + (setf start annotation-index)) + (invoke-annotation stream annotation nil))) + (when (> end start) + (write-string buffer target :start start :end end)))) + + (defun flush-annotations (stream end truncatep) + (let ((end-posn (index-posn end stream))) + (loop + for annotation = (dequeue-annotation stream :end-posn end-posn) + while annotation + do (invoke-annotation stream annotation truncatep)))) + + ;;; + ;;; Changed functions + ;;; + + (defun maybe-output (stream force-newlines-p) + (declare (type pretty-stream stream)) + (let ((tail (pretty-stream-queue-tail stream)) + (output-anything nil)) + (loop + (unless tail + (setf (pretty-stream-queue-head stream) nil) + (return)) + (let ((next (pop tail))) + (etypecase next + (newline + (when (ecase (newline-kind next) + ((:literal :mandatory :linear) t) + (:miser (misering-p stream)) + (:fill + (or (misering-p stream) + (> (pretty-stream-line-number stream) + (logical-block-section-start-line + (first (pretty-stream-blocks stream)))) + (ecase (fits-on-line-p stream + (newline-section-end next) + force-newlines-p) + ((t) nil) + ((nil) t) + (:dont-know + (return)))))) + (setf output-anything t) + (output-line stream next))) + (indentation + (unless (misering-p stream) + (set-indentation stream + (+ (ecase (indentation-kind next) + (:block + (logical-block-start-column + (car (pretty-stream-blocks stream)))) + (:current + (posn-column + (indentation-posn next) + stream))) + (indentation-amount next))))) + (block-start + (ecase (fits-on-line-p stream (block-start-section-end next) + force-newlines-p) + ((t) + ;; Just nuke the whole logical block and make it look like one + ;; nice long literal. (But don't nuke annotations.) + (let ((end (block-start-block-end next))) + (expand-tabs stream end) + (re-enqueue-annotations stream end) + (setf tail (cdr (member end tail))))) + ((nil) + (really-start-logical-block + stream + (posn-column (block-start-posn next) stream) + (block-start-prefix next) + (block-start-suffix next))) + (:dont-know + (return)))) + (block-end + (really-end-logical-block stream)) + (tab + (expand-tabs stream next)) + (annotation + (re-enqueue-annotation stream next)))) + (setf (pretty-stream-queue-tail stream) tail)) + output-anything)) + + (defun output-line (stream until) + (declare (type pretty-stream stream) + (type newline until)) + (let* ((target (pretty-stream-target stream)) + (buffer (pretty-stream-buffer stream)) + (kind (newline-kind until)) + (literal-p (eq kind :literal)) + (amount-to-consume (posn-index (newline-posn until) stream)) + (amount-to-print + (if literal-p + amount-to-consume + (let ((last-non-blank + (position #\space buffer :end amount-to-consume + :from-end t :test #'char/=))) + (if last-non-blank + (1+ last-non-blank) + 0))))) + (output-buffer-with-annotations stream amount-to-print) + (flush-annotations stream amount-to-consume nil) + (let ((line-number (pretty-stream-line-number stream))) + (incf line-number) + (when (and (not *print-readably*) + (pretty-stream-print-lines stream) + (>= line-number (pretty-stream-print-lines stream))) + (write-string " .." target) + (flush-annotations stream + (pretty-stream-buffer-fill-pointer stream) + t) + (let ((suffix-length (logical-block-suffix-length + (car (pretty-stream-blocks stream))))) + (unless (zerop suffix-length) + (let* ((suffix (pretty-stream-suffix stream)) + (len (length suffix))) + (write-string suffix target + :start (- len suffix-length) + :end len)))) + (throw 'line-limit-abbreviation-happened t)) + (setf (pretty-stream-line-number stream) line-number) + (write-char #\newline target) + (setf (pretty-stream-buffer-start-column stream) 0) + (let* ((fill-ptr (pretty-stream-buffer-fill-pointer stream)) + (block (first (pretty-stream-blocks stream))) + (prefix-len + (if literal-p + (logical-block-per-line-prefix-end block) + (logical-block-prefix-length block))) + (shift (- amount-to-consume prefix-len)) + (new-fill-ptr (- fill-ptr shift)) + (new-buffer buffer) + (buffer-length (length buffer))) + (when (> new-fill-ptr buffer-length) + (setf new-buffer + (make-string (max (* buffer-length 2) + (+ buffer-length + (floor (* (- new-fill-ptr buffer-length) + 5) + 4))))) + (setf (pretty-stream-buffer stream) new-buffer)) + (replace new-buffer buffer + :start1 prefix-len :start2 amount-to-consume :end2 fill-ptr) + (replace new-buffer (pretty-stream-prefix stream) + :end1 prefix-len) + (setf (pretty-stream-buffer-fill-pointer stream) new-fill-ptr) + (incf (pretty-stream-buffer-offset stream) shift) + (unless literal-p + (setf (logical-block-section-column block) prefix-len) + (setf (logical-block-section-start-line block) line-number)))))) + + (defun output-partial-line (stream) + (let* ((fill-ptr (pretty-stream-buffer-fill-pointer stream)) + (tail (pretty-stream-queue-tail stream)) + (count + (if tail + (posn-index (queued-op-posn (car tail)) stream) + fill-ptr)) + (new-fill-ptr (- fill-ptr count)) + (buffer (pretty-stream-buffer stream))) + (when (zerop count) + (error "Output-partial-line called when nothing can be output.")) + (output-buffer-with-annotations stream count) + (incf (pretty-stream-buffer-start-column stream) count) + (replace buffer buffer :end1 new-fill-ptr :start2 count :end2 fill-ptr) + (setf (pretty-stream-buffer-fill-pointer stream) new-fill-ptr) + (incf (pretty-stream-buffer-offset stream) count))) + + (defun force-pretty-output (stream) + (maybe-output stream nil) + (expand-tabs stream nil) + (re-enqueue-annotations stream nil) + (output-buffer-with-annotations stream + (pretty-stream-buffer-fill-pointer stream))) + \ No newline at end of file -- Matthias Koeppe -- http://www.math.uni-magdeburg.de/~mkoeppe

1 1

[slime-devel] Running CL code from elisp, and vice versa
by Harald Hanche-Olsen 13 Feb '06

13 Feb '06

Is there a convenient function for running bits of CL code (in the backend common lisp of course) from elisp? I've been playing around with slime-eval-with-transcript and slime-eval-async, with rather mixed success. Most commonly, I just get a protocol error and lose my slime connection. Am I looking in the wrong place, perhaps? Why do I want this? Say I am editing some (non-lisp) file and then want to process it by feeding the filename to some function in the CL backend. I'd like to be able to just run something like (slime-eval-thing `(process-file ,(buffer-file-name)) ":cl-user") and have the backend lisp run (process-file "/foo/bar") or whatever. And, while we're at it, how about the backend lisp asking emacs to run some elisp code? Most importantly, I want to be able to have the backend ask emacs to open a file, and perhaps move to a specified point in the file. I notice that the debugger seems able to do this, so surely, the functionality exist. But how accessible is it to the user? - Harald

2 2

[slime-devel] Editor Slime/Configuration
by Robert McAlpine 13 Feb '06

13 Feb '06

Hi, I'm using Aquamacs 0.9.8 and still getting to grips with lisp/slime etc etc These are probably just dumb emacs questions: I'd like to stop the REPL from converting the text to bold on execution/completion of the entered form. (it makes it hard to read on the LCD with anti-aliasing). ... and if at all possible I'd like to turn on syntax colouring in the REPL. (I've played with the customizations.el file and changed a couple of slime-repl ... forms but not got the results I'd like). Any pointers would be appreciated, Robert

3 3

[slime-devel] prompting the user from Lisp
by Taylor Campbell 12 Feb '06

12 Feb '06

The SLIME protocol currently provides, I believe, two operations for reading input from the Emacs user: the READ-STRING mechanism and a simple Y-OR-N-P device. In order to prompt the user for specific input, one must send a string to Emacs and then parse a string read from Emacs, but this is all line-oriented and provides no fancy input mechanisms on the user's side, such as completion, so it's hard to offer a convenient prompt to the user from the Lisp side, such as in restart functions. Does it sound like a good idea to define a (:PROMPT <prompt string> <input type>) RPC to be called from Lisp? For instance, a USE-VALUE restart might send (:PROMPT "Value to use instead:" EXPRESSION) to request input from the user, rather than printing the prompt directly to standard output and reading from standard input, as is usually done now. This way, Emacs would be given more leeway in presenting the prompt -- e.g., it might use the typein window instead of cluttering the REPL buffer --, and it would allow for completion, editing not restricted to lines (like the usual REPL prompt), &c. It is probably pretty easy to implement; I'll experiment with it soon, but I wondered what others thought about the matter.

1 0

[slime-devel] problems with dettachtty
by Nicolas Lamirault 11 Feb '06

11 Feb '06

hello, slime words very well with my Emacs configuration. I would like to use it with dettachtty, but i can't. i use : SBCL 0.9.7.1 and i have juste make a cvs update (last changelog entry 02/06/2006) so, i try to launch slime like this : $> detachtty --dribble-file /tmp/.dribble --log-file /tmp/.detachtty --pid-file /tmp/.pid /tmp/.socket \ /usr/bin/sbcl \ --eval "(push \"/home/nicolas/src/slime/\" asdf:*central-registry*)" \ --eval "(asdf:operate 'asdf:load-op :swank)" \ --eval "(setq swank:*use-dedicated-output-stream* nil)" --eval "(swank:create-swank-server 4008)" but i have an error (file attached to this mail) someone know how can i do to use slime with detachtty ? thanks for any help -- Nicolas Lamirault

2 1

[slime-devel] problem with utf-8
by Nicolas Lamirault 11 Feb '06

11 Feb '06

hello, i must read a file encoded in utf-8 if i read this file from sbcl started in an xterm, i haven't got any error. i try to make this operation in my SLIME environment, but i have an error. so i put this in my emacs's configuration : (setq slime-net-coding-system 'utf-8-unix) but after this i can't start slime this is the error : Debugger entered--Lisp error: (cl-assertion-failed default-enable-multibyte-characters) signal(cl-assertion-failed (default-enable-multibyte-characters)) (or default-enable-multibyte-characters (signal (quote cl-assertion-failed) (list ...))) (progn (or default-enable-multibyte-characters (signal ... ...)) nil) (assert default-enable-multibyte-characters) (progn (assert default-enable-multibyte-characters)) (if (and (second props) (boundp ...)) (progn (assert default-enable-multibyte-characters))) (when (and (second props) (boundp ...)) (assert default-enable-multibyte-characters)) (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(utf-8-unix) (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 --cl-keys-- ...)) (block slime-start (let ... ... ...))) slime-start(:program "/usr/bin/sbcl" :program-args nil) apply(slime-start (:program "/usr/bin/sbcl" :program-args nil)) slime() call-interactively(slime) execute-extended-command(nil) call-interactively(execute-extended-command) have you got an idea for this problem ? thanks -- Nicolas Lamirault

3 2

[slime-devel] Not possible to inspect method slots in Lispworks
by Luke Crook 10 Feb '06

10 Feb '06

In the latest version of SLIME from CVS for Lispworks, I receive the following error when I attempt to inspect the values for a slot in an object: >> The slot #<STANDARD-EFFECTIVE-SLOT-DEFINITION A-METHOD 21C8CD0C> is missing from #<A-CLASS 21C8D174> (of class #<STANDARD-CLASS A-CLASS 21C4734C>), when reading the value. << This is for the following: CL-USER> (defclass a-class () ((a-method :accessor a-method))) #<STANDARD-CLASS A-CLASS 21C4734C> CL-USER> (make-instance 'a-class) #<A-CLASS 21C8D174> This used to work in the SLIME CVS version of perhaps a month or so ago. -Luke

3 3

[slime-devel] macro-indentation should ignore &optional
by darkness 10 Feb '06

10 Feb '06

Greetings. I've got a macro like: (defmacro tbf (&optional bar &body baz) ...) With SLIME from CVS, this gets indented as: (tbf (:arg value) (form1) (form2)) Whereas I think the correct indentation should be: (tbf (:arg value) (form1) (form2)) The problem (as I see it) is that swank:macro-indent counts &optional as an argument, rather than as a lambda list keyword. Below is a simple patch against SLIME CVS. =================================================================== RCS file: /project/slime/cvsroot/slime/swank.lisp,v retrieving revision 1.360 diff -u -r1.360 swank.lisp --- swank.lisp 6 Feb 2006 18:42:09 -0000 1.360 +++ swank.lisp 9 Feb 2006 17:16:26 -0000 @@ -4369,7 +4369,7 @@ (defun macro-indentation (arglist) (if (well-formed-list-p arglist) - (position '&body (clean-arglist arglist)) + (position '&body (remove '&optional (clean-arglist arglist))) nil)) (defun well-formed-list-p (list)

2 1

[slime-devel] Emacs freezing bug fix
by Timofei Shatrov 10 Feb '06

10 Feb '06

I found a fix for a bug that plagued me for a long time. Whenever I was connected to Internet, Slime was consistently hanging Emacs cold. The bug apparently stems from make-network-process function of Emacs which demonstrates the same behavior. Anyway, there is a fix: replace all occurences of "127.0.0.1" in slime.el with "localhost" - surprisingly this solves the problem. -- Best regards, Timofei Shatrov mailto:grue@mail.ru

2 1

RE: [slime-devel] Re: Slime inserting an extra parenthesis
by Bradford W Miller 08 Feb '06

08 Feb '06

I smell a project: http://www.rci.rutgers.edu/~cfs/472_html/Planning/PlanRecog.html Unfortunately, it's close enough to my day job I'd have IP problems doing the work. But I'd be happy to kibitz. -----Original Message----- From: slime-devel-bounces(a)common-lisp.net [mailto:slime-devel-bounces@common-lisp.net] On Behalf Of edi(a)agharta.de Sent: Tuesday, February 07, 2006 6:49 AM To: jan(a)rychter.com Cc: slime-devel(a)common-lisp.net Subject: Re: [slime-devel] Re: Slime inserting an extra parenthesis On Tue, 07 Feb 2006 10:27:40 +0100, Jan Rychter <jan(a)rychter.com> wrote: > Right, well -- but shouldn't completion be smart enough to know if > the parentheses should be closed or not? At the moment I can't really imagine how SLIME should be able to always do The Right Thing[TM] unless it can read your mind. But I think patches are always welcome. _______________________________________________ slime-devel site list slime-devel(a)common-lisp.net http://common-lisp.net/mailman/listinfo/slime-devel

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel February 2006