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

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

09 Apr '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.662 slime/ChangeLog:1.663 --- slime/ChangeLog:1.662 Thu Apr 7 12:00:40 2005 +++ slime/ChangeLog Sat Apr 9 09:08:21 2005 @@ -1,3 +1,25 @@ +2005-04-09 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (sldb-get-buffer): Create a fresh buffer if there's no + buffer for the connection (and don't reuse an existing buffer even + if it has a matching name). + (slime-buffer-visible-p, slime-ir1-expand): Delete unused + functions. Mark some others as unused, but leave them there + because they are potentially useful. + + * swank.lisp (with-io-redirection, with-connection) + (with-buffer-syntax): Implement macros with a `call-with' + functions to avoid some code bloat. + (call-with-connection, maybe-call-with-io-redirection) + (call-with-buffer-syntax): New functions. + (interactive-eval): Use from-string instead of read-from-string to + avoid problems whit *read-suppress*. + + * swank-sbcl.lisp: Add a few comments. + + * swank-abcl.lisp (print-frame): Trim whitespace to make the + backtrace look a bit terser. + 2005-04-07 Helmut Eller <heller(a)common-lisp.net> * slime.el (slime-net-coding-system): More fixes for

1 0

[slime-devel] Re: [slime-cvs] CVS update: slime/doc/slime.texi
by Luke Gorrie 08 Apr '05

08 Apr '05

[Did this post not make it to the list yesterday?] heller(a)common-lisp.net (Helmut Eller) writes: > Modified Files: > slime.texi > Log Message: > Mention Unicode support and some multi-threading issues. Cool. I added some notes about the new inspector. I wonder if we're actually using the INSPECTOR argument to INSPECT-IN-EMACS anywhere? Can we remove it, or? I also documented slime-selector. I'm reproducing that section here since it's so bad that most people probably don't know about it: 6.1 `slime-selector' ==================== The `slime-selector' command is for quickly switching to important buffers: the REPL, SLDB, the Lisp source you were just hacking, etc. Once invoked the command prompts for a single letter to specify which buffer it should display. Here are some of the options: `?' A help buffer listing all `slime-selectors''s available buffers. `r' The REPL buffer for the current SLIME connection. `d' The most recently activated SLDB buffer for the current connection. `l' The most recently visited `lisp-mode' source buffer. `s' The `*slime-scratch*' buffer. *Note slime-scratch::. `slime-selector' doesn't have a key binding by default but we suggest that you assign it a global one. You can bind `C-c s' like this: (global-set-key "\C-cs" 'slime-selector) And then you can switch to the REPL from anywhere with `C-c s r'. The macro `def-slime-selector-method' can be used to define new buffers for `slime-selector' to find.

7 17

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

07 Apr '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.660 slime/ChangeLog:1.662 --- slime/ChangeLog:1.660 Tue Apr 5 15:41:23 2005 +++ slime/ChangeLog Thu Apr 7 12:00:40 2005 @@ -1,3 +1,10 @@ +2005-04-07 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-net-coding-system): More fixes for + non-mule-XEmacsen. + (slime-net-coding-system): Even more fixes to make it for + mule-XEmacs. + 2005-04-05 Juergen Gmeiner <gj(a)gjdv.at> * swank-lisworks.lisp (find-top-frame): If we can't find an

1 0

[slime-devel] problem with lambda gtk ?
by Nicolas Lamirault 07 Apr '05

07 Apr '05

hello, i have a problem with slime and lambda gtk i make a new sbcl.core image and when i start sbcl from shell with this image, i haven't got any problems : * sbcl --core ./sbcl-af.core This is SBCL 0.8.19.39, an implementation of ANSI Common Lisp. More information about SBCL is available at <http://www.sbcl.org/>. SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. * now i would like to use this new image with slime : C-u M-x slime Run lisp: sbcl --core /home/nicolas/src/lambdagtk/sbcl-af.core BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. * ; loading #P"/home/nicolas/src/slime/swank-loader.lisp" ;; loading #P"/home/nicolas/.slime/fasl/sbcl-0.8.19.39-linux-x86/swank-backend.fasl" ;; loading #P"/home/nicolas/.slime/fasl/sbcl-0.8.19.39-linux-x86/nregex.fasl" ;; loading #P"/home/nicolas/.slime/fasl/sbcl-0.8.19.39-linux-x86/swank-sbcl.fasl" debugger invoked on a SB-INT:EXTENSION-FAILURE in thread 9177: Don't know how to REQUIRE SB-BSD-SOCKETS. See also: The SBCL Manual, Variable SB-EXT:*MODULE-PROVIDER-FUNCTIONS* The SBCL Manual, Function REQUIRE You can type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [ABORT ] Reduce debugger level (leaving debugger, returning to toplevel). 1: [TOPLEVEL] Restart at toplevel READ/EVAL/PRINT loop. (SB-IMPL::REQUIRE-ERROR 3 "Don't know how to ~S ~A.")[:EXTERNAL] 0] any idea ? -- Nicolas Lamirault

3 3

[slime-devel] Fix for missing find-coding-system
by James McIlree 07 Apr '05

07 Apr '05

> Nathan Froyd <froydnj <at> cs.rice.edu> writes: > > > I'm running XEmacs 21.4.15 on OS X 10.3.8. I just updated my Slime > > to the newest, shiniest CVS version (from 1.0 or so), only to find > out > > that it won't work with my XEmacs. Near as I can tell, it's because > > my XEmacs isn't MULE-ized ({make,find}-coding-system do not exist) > and > > Slime really wants MULE or some semblance thereof to operate. I > > assume then that Slime does not support non-MULE emacsen...is this a > > correct assumption? > > The assumption is correct, but it's not much work to remove any > dependency on those functions. It should suffice, to provide dummy > functions for find-coding-system and check-coding-system which return > true for 'binary, and maybe a (if (fboundp 'set-process-coding-system)) > in slime-open-stream-to-lisp. > > I can't try a non-mule version myself, because the Debian "nomule" > versions still have find-coding-system. Also, if I configure CVS > XEmacs with --disable-mule, I still get find-coding-system as a > built-in function. > > Helmut. I ran exactly the same problem yesterday. After some experimentation, I found that xemacs 21.4.17 (latest stable) also does not define find-coding-system. When I built 21.4.17 with mule enabled, something in the font system became confused, making that an unpleasant fix. Xemacs 21.5.20 (beta) does define find-coding-system by default. To build on OS X, you need to specify --without-ldap to configure. I decided to stick with 21.4, and hacked the suggested diffs into slime.el. I'm a novice lisp coder, and a total novice to SLIME coding, so please feel free to change as needed to conform to good coding and style standards! I've tested with ACL & SBCL on OS X 10.3.8, and things started up and minimally worked without trouble. James McIlree diff -r1.478 slime.el 1491a1492,1507 > (if (not (fboundp 'find-coding-system)) > (defun find-coding-system (coding-system) > (if (eq coding-system 'binary) > coding-system > nil))) > > (if (not (fboundp 'check-coding-system)) > (defun check-coding-system (coding-system) > (if (eq coding-system 'binary) > coding-system > nil))) > > (if (not (fboundp 'process-coding-system)) > (defun process-coding-system (unused-and-ignored) > '(binary . binary))) > 2481,2483c2497,2500 < (set-process-coding-system stream < slime-net-coding-system < slime-net-coding-system) --- > (when (fboundp 'set-process-coding-system) > (set-process-coding-system stream > slime-net-coding-system > slime-net-coding-system))

4 3

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

05 Apr '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.659 slime/ChangeLog:1.660 --- slime/ChangeLog:1.659 Mon Apr 4 08:16:23 2005 +++ slime/ChangeLog Tue Apr 5 15:41:23 2005 @@ -1,3 +1,8 @@ +2005-04-05 Juergen Gmeiner <gj(a)gjdv.at> + + * swank-lisworks.lisp (find-top-frame): If we can't find an + invoke-debugger frame we take any old frame at the top. + 2005-04-04 James McIlree <ovrskeek(a)mac.com> * slime.el (find-coding-system, check-coding-system)

1 0

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

04 Apr '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.657 slime/ChangeLog:1.659 --- slime/ChangeLog:1.657 Fri Apr 1 23:57:42 2005 +++ slime/ChangeLog Mon Apr 4 08:16:23 2005 @@ -1,3 +1,30 @@ +2005-04-04 James McIlree <ovrskeek(a)mac.com> + + * slime.el (find-coding-system, check-coding-system) + (process-coding-system, set-process-coding-system): Dummy + functions for no-mule-XEmacsen. + +2005-04-04 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-repl-show-maximum-output): New + function. Immitate the scrolling behavior of a terminal. + (slime-with-output-end-mark, slime-repl-return) + (slime-repl-send-input, slime-display-output-buffer): Use it + (slime-lisp-implementation-version, slime-machine-instance): New + connection variables. Suggested by Eduardo Muñoz. + (slime-set-connection-info): Initialize them. + + * swank.lisp (connection-info): Include version and hostname in + the result. + + * swank-cmucl.lisp (breakpoint-values): Fixes for CMUCL-2005-03 + snapshot. + + * doc/slime.texi: Fix spelling errors. + + * cl-indent.el: Remove the file. Let the Emacs developers + maintain it. + 2005-04-01 Helmut Eller <heller(a)common-lisp.net> * slime.el (sldb-get-buffer): Initialize the buffer local

1 0

[slime-devel] SLIME and Allegro on Windows
by Peter Seibel 04 Apr '05

04 Apr '05

Does anyone know what the deal is with using Allegro on Windows with SLIME? As in, why it doesn't Just Work. (I've seen Bill Clementson's blog entry--that's the approved work around, right?) Is this something that Franz could fix by providing a console app version of alisp.exe (and one that doesn't have whatever multithreading problem build.exe (the console app version of mlisp.exe) has?) -Peter -- Peter Seibel peter(a)gigamonkeys.com Lisp is the red pill. -- John Fraser, comp.lang.lisp

2 1

[slime-devel] small patch to slime-xref-quit & feature request.
by Eduardo Muñoz 04 Apr '05

04 Apr '05

Using M-. with a generic function presents a buffer selection thingy. Selecting the desired method or defclass opens the desired buffer but then using q to exit the xrefs buffer restores de window configuration so I have to select the buffer manually. Using C-x o to exit the xref buffer leaves it visible but this is something I want to avoid. So I have installed locally the following patch: Index: slime.el =================================================================== RCS file: /project/slime/cvsroot/slime/slime.el,v retrieving revision 1.477 diff -u -r1.477 slime.el --- slime.el 1 Apr 2005 19:58:20 -0000 1.477 +++ slime.el 1 Apr 2005 21:07:24 -0000 @@ -6065,12 +6066,14 @@ (error "No context for finding locations.")) (funcall slime-next-location-function)) -(defun slime-xref-quit () - "Kill the current xref buffer and restore the window configuration." - (interactive) +(defun slime-xref-quit (arg) + "Kill the current xref buffer and restore the window configuration. +If arg is supplied do not restore configuration." + (interactive "P") (let ((config slime-xref-saved-window-configuration)) (slime-xref-cleanup) - (set-window-configuration config))) + (unless arg + (set-window-configuration config)))) (defun slime-xref-cleanup () "Delete overlays created by xref mode and kill the xref buffer." ---------------------------- The feature request is to send more arguments to slime-translate-to-lisp-filename-function and her sister slime-translate-from-lisp-filename-function, say (lisp-implementation-version) and (machine-instance). I am no elisp expert and failed to work out something like this. The idea is to be able to know if the translation is really needed (emacs on windows, lisp on linux) or not (everything on linux). The easy part is to know where emacs is running and the hard one (that I leave to fine slime hackers :) is to know the lisp host environment. Greetings, -- Eduardo Muñoz | (prog () 10 (print "Hello world!") http://213.97.131.125/ | 20 (go 10))

3 4

[slime-devel] GCL and slime
by Pekka NIiranen 03 Apr '05

03 Apr '05

Hi, why is GCL (http://savannah.gnu.org/projects/gcl/) not supported? -pekka-

3 2