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

[slime-devel] Parsing the in-package form
by Antonio Menezes Leitao 23 Nov '06

23 Nov '06

Hi, If I'm not mistaken, the current Slime version doesn't correctly parse in-package forms when the package name is a string or a keyword. This can be easily seen by writing in an edit buffer (in-package :foo) or (in-package "FOO") and then pressing C-c M-p (slime-repl-set-package) The following replacement correct this behaviour. (defun slime-search-buffer-package () (save-excursion (when (let ((case-fold-search t) (regexp "^(\\(cl:\\|common-lisp:\\)?in-package\\>[ \n\t\r':\"]*")) (or (re-search-backward regexp nil t) (re-search-forward regexp nil t))) (goto-char (match-end 0)) (let ((start (point))) (let ((pkg (ignore-errors (read (current-buffer))))) (and pkg (format "%S" pkg))))))) Best regards, António Leitão.

2 1

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

23 Nov '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1004 slime/ChangeLog:1.1005 --- slime/ChangeLog:1.1004 Tue Nov 21 17:00:22 2006 +++ slime/ChangeLog Wed Nov 22 10:29:23 2006 @@ -1,3 +1,7 @@ +2006-11-22 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-edit-definition): Don't hide error messages. + 2006-11-21 Helmut Eller <heller(a)common-lisp.net> * swank.lisp (*coding-system*): "Coding systems" are now strings

1 0

[slime-devel] compiling forms/regions/defuns with (optimize (debug 3) (speed 0) (safety 0))
by Marco Baringer 22 Nov '06

22 Nov '06

what do people think about a varient of slime-compile-defun which wrapped the code in (locally (declaim (optimize (speed 0) (safety 3) (debug 3))) ,@form) i'd bind this to C-u C-c C-c (and C-u C-c C-k) good idea? bad idea? -- -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

8 11

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

22 Nov '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1002 slime/ChangeLog:1.1004 --- slime/ChangeLog:1.1002 Sun Nov 19 16:25:15 2006 +++ slime/ChangeLog Tue Nov 21 17:00:22 2006 @@ -1,3 +1,8 @@ +2006-11-21 Helmut Eller <heller(a)common-lisp.net> + + * swank.lisp (*coding-system*): "Coding systems" are now strings + instead of keywords. + 2006-11-19 Helmut Eller <heller(a)common-lisp.net> * slime.el (slime-compile-file): Let the Lisp side choose the @@ -5,6 +10,8 @@ (slime-coding): Deleted. * swank.lisp (compile-file-for-emacs): Use guess-external-format. + (swank:create-server): no more accepts an :external-format 'enc , + use :coding-system "enc" instead. * swank-backend.lisp (find-external-format) (guess-external-format): New.

1 0

[slime-devel] Documentation patch for swank:create-server
by Ury Marshak 21 Nov '06

21 Nov '06

There seem to be some changes related to external-format that changed the interface of swank:create-server. When looking for the source of the breakage of my lisp startup I found that the description of swank:create-server is missing from the manual. This is a small (documentation only) patch that tries to fix this (using the new :coding-system syntax) Cheers, Ury Index: ChangeLog =================================================================== RCS file: /project/slime/cvsroot/slime/ChangeLog,v retrieving revision 1.1002 diff -u -r1.1002 ChangeLog --- ChangeLog 19 Nov 2006 21:25:15 -0000 1.1002 +++ ChangeLog 21 Nov 2006 14:59:31 -0000 @@ -5,6 +5,8 @@ (slime-coding): Deleted. * swank.lisp (compile-file-for-emacs): Use guess-external-format. + (swank:create-server): no more accepts an :external-format 'enc , + use :coding-system "enc" instead. * swank-backend.lisp (find-external-format) (guess-external-format): New. Index: doc/slime.texi =================================================================== RCS file: /project/slime/cvsroot/slime/doc/slime.texi,v retrieving revision 1.48 diff -u -r1.48 slime.texi --- doc/slime.texi 20 Sep 2006 18:37:47 -0000 1.48 +++ doc/slime.texi 21 Nov 2006 14:59:32 -0000 @@ -1460,10 +1460,8 @@ inside a running lisp image@footnote{@SLIME{} also provides an @acronym{ASDF} system definiton which does the same thing}. Now all we -need to do is startup our swank server. This example assumes we're -using the default settings, if you need to do anything particular -(like be able to reconnect to swank after you're done, look into -@code{swank:create-server}'s other arguments). +need to do is startup our swank server. The first example assumes we're +using the default settings. @example (swank:create-server) @@ -1480,6 +1478,37 @@ (setf swank:*use-dedicated-output-stream* nil) @end example +If you need to do anything particular +(like be able to reconnect to swank after you're done), look into +@code{swank:create-server}'s other arguments. Some of these arguments +are +@table @code + +@item :PORT +Port number for the server to listen on (default: 4005). +@item :STYLE +See @xref{Communication style}. +@item :DONT-CLOSE +Boolean indicating if the server will continue to accept connections +after the first one (default: @code{NIL}). For ``long-running'' lisp processes +to which you want to be able to connect from time to time, +specify @code{:dont-close t} +@item :CODING-SYSTEM +String designating the encoding to be used to communicate between the Emacs and Lisp. +@end table + +So the more complete example will be +@example +(swank:create-server :port 4005 :dont-close t :coding-system "utf-8-unix") +@end example +On the emacs side you will use something like +@example +(setq slime-net-coding-system 'utf-8-unix) +(slime-connect "127.0.0.1" 4005)) +@end example +to connect to this lisp image from the same machine. + + @node Setting up Emacs @subsection Setting up Emacs

2 1

[slime-devel] Re: SLIME Committers
by Attila Lendvai 21 Nov '06

21 Nov '06

> Could you give CVS write permissions for SLIME to the following > people? > > Jeffrey Cunningham <jeffrey(a)cunningham.net> > Attila Lendvai attila.lendvai(a)gmail.com thanks Helmut! as you seems to be the long missed dictator (or even if you are not, you have been stamped by this :) what do you and the others think about (1) moving the darcs repo at http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cl-wdim-slime;a=summ… under /project/slime? and (2) advertising it as the primary repository? sorry for pushing it that much, but i honestly think that it would make everyone's life (including me) easier on the long run. in case there are people who strongly disagree with this, please speak up and tell your reasons. if it turned out to be desired (which may have been signaled by a long enough silence) i'd voulenteer to do the job. -- - attila "- The truth is that I've been too considerate, and so became unintentionally cruel... - I understand. - No, you don't understand! We don't speak the same language!" (Ingmar Bergman - Smultronstället)

6 11

[slime-devel] What exactly means slime menu item "compilation system"?
by commi 17 Nov '06

17 Nov '06

Hello, when using slime i have a menu item in emacs called " slime -> compilation -> system". does "system" mean asdf-system? i cannot find any info in chapter 3.2.1 of the slime manual. Thanks for any pointers, commi

1 0

[slime-devel] Re: Documentation project
by Jeffrey Cunningham 15 Nov '06

15 Nov '06

On Tue Nov 14, 2006 at 08:07:59PM -0800, Jeffrey Cunningham wrote: > Before I get too far along here, I thought I'd see if I'm on the right > track. I've attached a pdf I produced after working on the > documentation for the last few days. > > The biggest additions are two Appendices: a key-bindings index and a > function index. Entries in both these are linked to anchors where the > functions are discussed. > > I've added a number of undocumented functions and in the process found > it difficult to stick to the exact way they were grouped before. So I > took the liberty of re-arranging some of the subsections slightly and > adding a couple more. > > Some of the functions have no descriptions - I didn't understand these > well enough to describe them myself. I will leave these to others to > document, but the placeholders will be there. > > I am planning on finishing adding all the functions which are > accessible directoy, adding a lot more cross-links to anchors, and > also more examples. > > I assume there is no reason to document internal functions (or is > there?) > > Feedback would be helpful. > > --Jeff > Well, that didn't work - apparently one cannot include attachments in emails to the list. Here's a link where you can get the attachment: http://makewavs.com/lisp/slime.pdf --Jeff

2 1

[slime-devel] Question on Downloading and installing SLIME to EMACS
by Brian Jones 15 Nov '06

15 Nov '06

Hello, I am trying to download and install the latest version of SLIME into emacs. The operating system I am running is Ubuntu Linux. To configure the CVSROOT, would I type this command (export CVSROOT=:pserver:anonymous@common-lisp.net:/project/slime/cvsroot) in the bash terminal? Would I log in the same way with the password "anonymous"? My second question deals with the installation process. As I've said before I am running Ubuntu Linux and I was wondering how I would find the path to my lisp system and the path to my slime directory. Any help would be greatly appreciated. Ichben E.

3 2

[slime-devel] macroexpand window
by Giorgos Pontikakis 15 Nov '06

15 Nov '06

Hello all, I have just upgraded slime to the current version from cvs and I have the following questions: 1. In emacs, let's say I have two open windows in the same frame. The first is the REPL and the second some lisp file. When I macroexpand an expression with C-c RET, say from the REPL, the result of the macroexpansion appears in the window with the lisp file. Up to here, fine, but, when I press `q' to close the macroexpansion, the window where it appeared is deleted (in my example only the REPL remains). In previous versions, the window remained intact and its former contents appeared again. I find that the old behaviour was much more convenient. I think the current behaviour is expected only if there is only one window originally and the macroexpansion itself causes the second window to open. So, is it a bug or is it intentional? If the latter is true, is there a simple way for me to revert the old behaviour (I suppose changing something in slime.el or what?) 2. I recently read in this list about some fuzzy completion patches. I thought that those just added new behaviour and I could use the old behaviour. But either I got a false impression or I cannot find the correct settings. Again, how can I revert to the old behaviour? If this matters, I use GNU Emacs 22.0.50.1 on linux, with SBCL 0.9.12 Thanks in advance, -- Giorgos

3 3