slime-devel June 2008

slime-devel@common-lisp.net

24 participants
26 discussions

[slime-devel] Saving *slime-scratch*
by Nikodemus Siivola 11 Oct '08

11 Oct '08

The attached patch associates *slime-scratch* with a file if you name one as "slime-scratch-file". I've been running slime with this a while, and rather like it. Something like this was talked about a while ago, and dropped because of what looked like an ideologinal objection to scratch-buffers in my mind. Is the consensus still against this? Cheers, -- Nikodemus Index: slime.el =================================================================== RCS file: /project/slime/cvsroot/slime/slime.el,v retrieving revision 1.784 diff -u -r1.784 slime.el --- slime.el 16 Apr 2007 14:42:33 -0000 1.784 +++ slime.el 27 Apr 2007 13:26:17 -0000 @@ -4570,10 +4570,15 @@ (set-keymap-parent map lisp-mode-map) map)) +(defvar slime-scratch-file nil) + (defun slime-scratch-buffer () "Return the scratch buffer, create it if necessary." (or (get-buffer "*slime-scratch*") - (with-current-buffer (get-buffer-create "*slime-scratch*") + (with-current-buffer (if (not slime-scratch-file) + (get-buffer-create "*slime-scratch*") + (find-file slime-scratch-file)) + (rename-buffer "*slime-scratch*") (lisp-mode) (use-local-map slime-scratch-mode-map) (slime-mode t)

4 5

[slime-devel] slime-c-p-c
by Madhu 08 Sep '08

08 Sep '08

Re: slime-complete-symbol* : I noticed that slime-c-p-c does not work correctly but can mangle text after a completion is chosen , [I'm appending a test case to the end of this message.] I'm afraid I'm to blame for this, I think: the patch I submitted claiming to fix XEmacs behaviour (on 2007-08-04) and which was committed on 2007-09-04 is incorrect [ 1. the analysis is not restricted to XEmacs, and 2. Emacs choose-completion does not work right unless the text in the buffer is a proper prefix of the completions displayed. I cannot see any lowest-common-denominator solution for this.] I would suggest reverting the patch. The downside is that you get back the original behaviour, which mangles the text BEFORE the completion is chosen: If you type "m-v" and hit TAB the function will delete your text and leave you with "m" -- because "m" is emacs' completed-prefix matching both "machine-version" and "multiple-value*"s. [This may or may not be acceptable, indeed whether it is what you want would depend on which buffer you are in, and what symbol you are trying to complete] Apologies for the incomplete patch and the earlier noise over the [unrelated yet related] unambiguous-prefix issue (from 06).. -- Madhu ;;; PS: Here is a test case transcript, and also what to expect on the ;;; suggest fix : ;;; ;;; 1. First we recreate the situation in acl, where there are multiple ;;; completions for "l-p-t". ;;; CL-USER> '(locale-print-time logical-pathname-translations logical-pathname-translations-database-pathnames) (LOCALE-PRINT-TIME LOGICAL-PATHNAME-TRANSLATIONS LOGICAL-PATHNAME-TRANSLATIONS-DATABASE-PATHNAMES) ;;; ;;; 2. slime-c-p-c-unambiguous-prefix-p is set to nil ;;; BEFORE: CL-USER> l-p-t ;;; ^^^ hit TAB, then choose the logical-pathname-translations ;;; completion in the *Completions* buffer ;;; AFTER: The completed form looks like: CL-USER> (l-plogical-pathname-translations ;;; ;;; 3. Next try after setting slime-c-p-c-unambiguous-prefix-p nil ;;; BEFORE: CL-USER> l-p-t ;;; ^^^ hit TAB, then choose the logical-pathname-translations ;;; completion in the *Completions* buffer ;;; AFTER: CL-USER> (logical-pathname-translationsp-t ;;; ;;; 4.WITH 2007-09-04 PATCH REVERTED: ;;; BEFORE: CL-USER> l-p-t ;;; ^^^ hit TAB, then choose the logical-pathname-translations ;;; completion in the *Completions* buffer ;;; AFTER: CL-USER> (lo ^^^ note that the text you input is gone. ;;; but at least choosing a completion won't mangle the text in your ;;; buffer

1 1

[slime-devel] [PATCH] fix the indentation of IF forms in the slime-indentation contrib
by Luis Oliveira 20 Aug '08

20 Aug '08

Hello, The attached patch changes the indentation of IF forms from (if foo bar baz) to (if foo bar baz) which is, AFAIK, the most widespread way of indenting IF forms. Also, this patch <http://common-lisp.net/~loliveira/patches/slime-changelog-nuke-trailing-whi…> removes lots of trailing whitespace from the ChangeLog via M-x delete-trailing-whitespace. -- Luís Oliveira http://student.dei.uc.pt/~lmoliv/

2 2

[slime-devel] Unicode support for CMUCL
by Raymond Toy 19 Aug '08

19 Aug '08

Here is a small patch to enable support for Unicode for CMUCL. Seems to work. May need some more work on the *external-format-to-coding-system*, but iso-8859-1 and utf-8 appear to work ok, for the little bit of testing I've done. Ray --- swank-cmucl.lisp-orig 2008-06-01 18:06:07.000000000 -0400 +++ swank-cmucl.lisp 2008-06-01 18:01:44.000000000 -0400 @@ -99,10 +99,13 @@ (ext:close-socket fd))) (defimplementation accept-connection (socket &key - external-format buffering timeout) - (declare (ignore timeout external-format)) + external-format buffering timeout) + (declare (ignore timeout)) (let ((buffering (or buffering :full))) - (make-socket-io-stream (ext:accept-tcp-connection socket) buffering))) + (make-socket-io-stream (ext:accept-tcp-connection socket) + buffering + :external-format + (or external-format :iso-8859-1)))) ;;;;; Sockets @@ -117,10 +120,23 @@ (let ((hostent (ext:lookup-host-entry hostname))) (car (ext:host-entry-addr-list hostent)))) -(defun make-socket-io-stream (fd buffering) +(defvar *external-format-to-coding-system* + '((:iso-8859-1 + "latin-1" "latin-1-unix" "iso-latin-1-unix" + "iso-8859-1" "iso-8859-1-unix") + (:utf-8 "utf-8" "utf-8-unix"))) + +(defimplementation find-external-format (coding-system) + (car (rassoc-if (lambda (x) (member coding-system x :test #'equal)) + *external-format-to-coding-system*))) + + +(defun make-socket-io-stream (fd buffering &key external-format) "Create a new input/output fd-stream for FD." (sys:make-fd-stream fd :input t :output t :element-type 'base-char - :buffering buffering)) + :buffering buffering + #+unicode :external-format + #+unicode external-format)) ;;;;; Signal-driven I/O

3 7

[slime-devel] Mercurial
by Helmut Eller 08 Aug '08

08 Aug '08

What do people think of switching from CVS to Mercurial[*] ? Helmut. [*] http://www.selenic.com/mercurial/

20 50

[slime-devel] Output lost after disconnect reconnect
by Gábor Melis 29 Jul '08

29 Jul '08

After a disconnect, reconnect long running worker threads that were spawn for instance by C-x C-e in a lisp buffer send their output to the void. Detailed process to reproduce: 1. start an sbcl 2. (require 'asdf) (asdf:oos 'asdf:load-op 'swank) (setq swank:*globally-redirect-io* t) (setq swank:*global-debugger* t) (setf swank:*use-dedicated-output-stream* nil) (swank:create-server :dont-close t :port 4007) 3. connect from slime 4. from a buffer eval (loop (sleep 5) (print 'hello *trace-output*) (force-output *trace-output*)) 5. disconnect [At this point output should be going to the terminal where sbcl was started which is the case when the above snippet is wrapped in (sb-thread:make-thread (lambda () ...))). Instead it goes to nowhere.] 6. slime-connect again 7. observe that nobody says hello anymore The attached patch aims to fix this by: * swank.lisp (maybe-call-with-io-redirection): don't CALL-WITH-REDIRECTED-IO if *GLOBALLY-REDIRECT-IO*. Fixes lost output after disconnect, reconnect. Cheers, Gábor Melis

2 5

[slime-devel] stepping
by Roman Budzianowski 05 Jul '08

05 Jul '08

Hi, Somehow, it doesn't work in my allegro, using SLIME PQ> (defun fact (n) (if (= n 1) 1 (* n (fact (1- n))))) FACT PQ> (fact 3) 6 PQ> (compile 'fact) FACT NIL NIL PQ> :step nil NIL PQ> (step fact) (FACT) PQ> (fact 3) 6 PQ> I'd appreciate any suggestions. Roman

3 3

[slime-devel] slime-read-interactive-args
by Harald Hanche-Olsen 04 Jul '08

04 Jul '08

Quoth the docstring of slime-read-interactive-args: - If the prefix-arg is `-', prompt for one of the registered lisps. There is just one small problem with this: There is no way (that I know of) to get a prefix arg on an emacs running under a tty. How about changing the condition to include any negative argument? This bites me just often enough to be annoying. - Harald

3 4

[slime-devel] Patch: Source location of methods (Allegro)
by Willem Broekema 04 Jul '08

04 Jul '08

The below patch works around the issue that Allegro does not record the source file location for methods defined inside a defgeneric form. The idea is that if the source location of a method is not found, then the defgeneric form is almost certainly the right place. For example: (defgeneric foo (x) (:method ((x fixnum)) (/ 1 0))) Calling (foo 123) and hitting "v" in the traceback would result in "Unknown source location for (method common-lisp-user::foo)" but with the patch leads correctly to the defgeneric form. (For methods defined outside the defgeneric form, the source location recording works fine.) *** swank-allegro.lisp 10 Jun 2008 19:55:30 +0200 1.102 --- swank-allegro.lisp 10 Jun 2008 21:19:20 +0200 *************** *** 414,419 **** --- 414,426 ---- (fspec-definition-locations next))) (t (let ((defs (excl::find-source-file fspec))) + (when (and (null defs) + (listp fspec) + (string= (car fspec) '#:method)) + ;; If methods are defined in a defgeneric form, the source location is + ;; recorded for the gf but not for the methods. Therefore fall back to + ;; the gf as the likely place of definition. + (setq defs (excl::find-source-file (second fspec)))) (if (null defs) (list (list (list nil fspec)

2 1

[slime-devel] PATCH: slime-qualify-cl-symbol-name
by kroger.lists＠gmail.com 04 Jul '08

04 Jul '08

Hi, If the user uses slime-call-defun in a file without a package defined the function in the repl will have a nil package like (nil::foo ). The attached patch fixes it. (I know that it's not a good style to develop without packages, but I teach using slime and it's good not to use packages in the beginning) Cheers, Pedro

2 1

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 2008