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

[slime-devel] completion for directories that start with a space (Mac)
by Jean-Christophe Helary 01 Feb '07

01 Feb '07

I am just starting Practical Common Lisp (again) with the Fink (unstable) carbon emacs/slime and I don't get slime to do proper completion when the first character of the directory to complete is a space. Even if I enter "\ "before the stripped directory name I can't get slime to complete it. My only solution is to use the mouse on the completion table. Is there anything I missed ? Jean-Christophe Helary

1 0

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 01 Feb '07

01 Feb '07

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1061 slime/ChangeLog:1.1062 --- slime/ChangeLog:1.1061 Tue Jan 30 17:23:39 2007 +++ slime/ChangeLog Wed Jan 31 08:23:52 2007 @@ -1,3 +1,8 @@ +2007-01-31 Marco Baringer <mb(a)bese.it> + + * slime.el (slime-repl-update-banner): Restore animation. + (slime-startup-animation): restore. + 2007-01-30 Helmut Eller <heller(a)common-lisp.net> * slime.el (slime-complete-symbol-function): Restore old default.

1 0

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 31 Jan '07

31 Jan '07

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1059 slime/ChangeLog:1.1061 --- slime/ChangeLog:1.1059 Mon Jan 29 18:43:17 2007 +++ slime/ChangeLog Tue Jan 30 17:23:39 2007 @@ -1,3 +1,14 @@ +2007-01-30 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-complete-symbol-function): Restore old default. + (set-keymap-parents): Deleted. + (slime-startup-animation): Deleted. + (slime-read-from-minibuffer): Don't use defun*. + (slime-repl-terminate-history-search): New. + (slime-repl-next-matching-input): Use it. + + * slime-autoloads.el: New file. + 2007-01-29 Sean O'Rourke <sorourke(a)cs.ucsd.edu> * slime.el (slime-start): Continue even if the user, after

1 0

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 30 Jan '07

30 Jan '07

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1058 slime/ChangeLog:1.1059 --- slime/ChangeLog:1.1058 Wed Jan 24 17:56:19 2007 +++ slime/ChangeLog Mon Jan 29 18:43:17 2007 @@ -1,3 +1,12 @@ +2007-01-29 Sean O'Rourke <sorourke(a)cs.ucsd.edu> + + * slime.el (slime-start): Continue even if the user, after + prompting, didn't recompile the stale .elc file. + (slime-urge-bytecode-recompile) [xemacs]: Abort immediately if the + user doesn't want to continue. + (slime-recompile-bytecode): Don't use byte-compile-warning-types; + it may not exist in XEmacs. + 2007-01-24 Helmut Eller <heller(a)common-lisp.net> * slime.el (sldb-recenter-region): Use count-screen-lines instead

1 0

[slime-devel] patch: make slime-urge-bytecode-recompile less irritating
by Sean O'Rourke 29 Jan '07

29 Jan '07

Recipe for frustration: * edit slime.el * save it in a state that you don't want to use immediately * M-x slime * "slime.elc is older than slime.el. Recompile/reload first? " No! * bang head on keyboard as slime petulantly refuses to start This patch makes the prompting non-fatal. /s Index: slime.el =================================================================== RCS file: /project/slime/cvsroot/slime/slime.el,v retrieving revision 1.753 diff -p -u -w -r1.753 slime.el --- slime.el 24 Jan 2007 22:55:13 -0000 1.753 +++ slime.el 26 Jan 2007 19:56:37 -0000 @@ -1549,8 +1551,8 @@ The rules for selecting the arguments ar :coding-system coding-system :init init :name name :init-function init-function))) (slime-check-coding-system coding-system) - (when (or (not (slime-bytecode-stale-p)) - (slime-urge-bytecode-recompile)) + (when (not (slime-bytecode-stale-p)) + (slime-urge-bytecode-recompile) (let ((proc (slime-maybe-start-lisp program program-args buffer))) (slime-inferior-connect proc args) (pop-to-buffer (process-buffer proc)))))) @@ -1650,13 +1652,11 @@ Warning: don't use this in XEmacs, it se (defun slime-urge-bytecode-recompile () "Urge the user to recompile slime.elc. Return true if we have been given permission to continue." - (if (featurep 'xemacs) + (unless (featurep 'xemacs) ;; My XEmacs crashes and burns if I recompile/reload an elisp ;; file from itself. So they have to do it themself. - (y-or-n-p "slime.elc is older than slime.el. Continue? ") - (if (y-or-n-p "slime.elc is older than slime.el. Recompile/reload first? ") - (progn (slime-recompile-bytecode) t) - nil))) + (when (y-or-n-p "slime.elc is older than slime.el. Recompile/reload first? ") + (slime-recompile-bytecode)))) (defun slime-abort-connection () "Abort connection the current connection attempt."

2 1

[slime-devel] New listener
by Liam Healy 29 Jan '07

29 Jan '07

Missing the old Symblics Select-L and Select-Control-L, I put together the following which will create a new listener and cycle through (forward or backward) the existing listeners. Comments welcome; I'm curious to know how to get slime-new-listener to work when the current listener is busy, because my main usage of a second listener is to do something while the first listener is busy, and unless I remember to open the second listener in advance, I'm still stuck. Liam

2 1

[slime-devel] [Re: SLIME manual fixes]
by Jeffrey Cunningham 29 Jan '07

29 Jan '07

I should have noticed that 'reply' went to Luke and not the list. J. ----- Forwarded message from Jeffrey Cunningham <jeffrey(a)cunningham.net> ----- On Sun Jan 21, 2007 at 02:32:32PM +0100, Luke Gorrie wrote: > The manual improvements look good, great work! > > Appendix A (index of keybindings) is excellent but I'm not sure that > Appendix B (index of functions) is worth its price in virtual trees. > Are there good "use cases" for it? > My reasoning was that if you want to find out what a function does without doing a text search it may be your only option. It isn't always clear what section you would find it in from the name alone. But what really induced me to add it was when an upgrade of xpdf at work broke its text search capability and all I had on that machine was slime.pdf. ;-) If no one else thinks it could be useful, I'll take it out. --Jeff ----- End forwarded message -----

9 24

[Fwd: Re: [slime-devel] Re: slime.el `slime-expand-abbreviations-and-complete']
by enometh＠meer.net 29 Jan '07

29 Jan '07

I know I said I didn't mind if this change was revered, but in the interest of correctness, I think the code Edi checked in again is plain wrong. Details below. ---------------------------- Original Message ---------------------------- Subject: Re: [slime-devel] Re: slime.el `slime-expand-abbreviations-and-complete' From: "Edi Weitz" <edi(a)agharta.de> Date: Sat, January 20, 2007 2:43 To: enometh(a)meer.net -------------------------------------------------------------------------- On 20 Jan 2007 10:34:55 -0000, Madhu <enometh(a)meer.net> wrote: > |However, I regularly use slime-complete-symbol* as my completion |function (but with other pop-up settings) and my text never got |garbled. And I liked the behaviour where point was directly > |after the shortest unambiguous prefix. > > With slime-complete-symbol* and a vanilla checkout, text gets > garbled again on emacs21. Perhaps the property setting shennanigans dont work on this emacs? > > I think you are have not considered all use cases and are also > ignoring the fact that if you are using emacs' `choose-completion' facility, you are not allowed to shift the point to an earlier > position during the completion operation. > > If you do wish to move the point, you should perhaps automatically invoke the completion command programatically again. I am not sure how this can be done. > > Even if it WFM, and provides a shiny feature, it should be clear that the existing code is wrong? I'd rather have this discussion on slime-devel if it's really necessary.

4 7

[slime-devel] Re: scripting via swank
by Alan Caulkins 27 Jan '07

27 Jan '07

On Fri, Jan 26, 2007 at 12:31:07PM +0100, Helmut Eller wrote: > * G�bor Melis [2007-01-25 19:09+0100] writes: > > > Ahoj > > > > Suppose there is a long running lisp image with a swank server and I > > want to connect to it from shell scripts and evaluate lisp forms in an > > environment where *standard-output*, *standard-input* and > > *error-output* are bound to streams that correspond to stdout, stdin > > and stderr of the shell script. > > > > The only idea I had was to pass the pid of the shell script to the lisp > > and bind *standard-output* to > > (open "/proc/<pid-of-shell-script/fd/0" ...) which should work on > > linux. I don't know that there is a good way to connect the shell script to the actual standard I/O in the Lisp image, but you might be able to get halfway there. You want a utility called nc (aka Netcat) that relays data between its stdin/stdout and sockets. It was designed to allow shell scripts to use streams to interface with network daemons and such. example: $ echo -n "GET / HTTP/1.0\r\n\r\n" | nc host.example.com 80 > file.html You'd have to listen on a socket in the Lisp, but once that connection is made, you could use stream I/O. Netcat works with UNIX domain sockets, so you wouldn't have to worry about TCP connections from other hosts. http://netcat.sourceforge.net/ man page: http://www.openbsd.org/cgi-bin/man.cgi?query=nc Another slightly less flexible possibility is Netpipes: http://web.purplefrog.com/~thoth/netpipes/netpipes.html -A -- Maxint Consulting Linux: The ultimate video game.

1 0

[slime-devel] [BUG] a repeatable way to crash a utf-8 slime session
by Samium Gromoff 27 Jan '07

27 Jan '07

While figuring out how to deal with unicode i stumbled upon across something which appeared to be killing slime session/sbcl with an ensuing emacs message telling something about process filters. Urfin from #lisp helped me to narrow this down to evaluation of (format t "~c" #\UD0BB), or otherwise getting #\UD0BB shown on the screen, like having it displayed as the result of evaluation. It seems to have a 100% repeatability. I have yesterday's slime and sbcl 1.0/x86/Linux. regards, Samium Gromoff

4 5