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

[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] Operating on the swank readtable?
by Alberto Riva 17 Jan '08

17 Jan '08

Hello, I'm trying to define a few macro characters for use in the slime top-level, but I can't figure out where to put the SET-DISPATCH-MACRO-CHARACTER calls so that they affect the swank readtable instead of the default one. I've tried putting them both in my lisp initialization file and in .swank.lisp, but in both cases the macro character is defined in the initial readtable and not in the slime one (so it works in the *inferior-lisp* buffer, but not in the slime-repl buffer). Thanks! Alberto Riva University of Florida

2 2

[slime-devel] slime apparently mis-reporting closed connection
by Samium Gromoff 26 Oct '07

26 Oct '07

After well into the second decade of slime-disconnect/slime-connect loop iteration (interweaved with normal operation) the emacs side of slime stopped recognising connection status. I`m doing a slime-disconnect, restarting swank and slime-connect, however immediately after this either a slime-load-file or a (load ...) in slime repl result in a message "Connection closed." i have some time before i will have to reboot the machine, and until then i can provide various forensics upon request... regards, Samium Gromoff

5 5

[slime-devel] Evaluate forms from within Lisp buffers and displaying the result in the REPL
by Rainer Joswig 26 Aug '07

26 Aug '07

Hi, I'm a bit used to the behavior of MCL when it comes to Lisp buffers and listeners. Maybe SLIME developers know how to achieve a similar behavior or would like to provide something similar. MCL allowed multiple Lisp text editor windows and listener windows. If there are multiple listeners one is the front most. If the cursor is behind a Lisp form in a Lisp editor window, one can press Enter (or control-return) and the form will be enqueued into the REPL of the front most listener. Doing this in a listener, the form will be displayed at the prompt and enqueued in the listener's REPL. Pressing Enter only has the effect that the form and the result is shown in the listener. In the Editor window, nothing happens (no cursor moved, no character entered, no window focus changed). The listener REPL gets the forms from its queue and displays the form and the result at the end of the current buffer. This way you get interaction histories in the listener. Currently SLIME lets me evaluate a form in a text buffer and the form gets printed into the listener and the result gets printed in the mini-buffer. I can see then in the listener the history of evaluated forms, but not the history of results. Additionally the form will be printed with additional characters before and after. SLIME displays several forms evaluated from a text buffer in the REPL like this: ;;;; (+ 1 2) ... ;;;; (+ 1 2) ... ;;;; (+ 1 2) ... The normal REPL interaction display would be like: CL-USER> (+ 1 2) 3 CL-USER> (+ 1 2) 3 CL-USER> (+ 1 2) 3 Both ways look different. Why not use the latter for both interactions? Useful is then also a command to rotate between the various listeners (next, previous) and Lisp buffers (next, previous). Advantages I see for MCL: * With MCL you get the same REPL listener display if you evaluate forms from the Lisp editor buffer (via RETURN) or if you use the REPL in the listener. * Using the enter key (vs. Return) to evaluate code in the editor gets rid of one complex keystroke. * One gets reusable interaction histories in the listener where form and result are displayed together. Is SLIME already providing something similar? Would others find this way of interaction between Lisp buffers and a REPL buffer useful? Regards, Rainer Joswig -- http://lispm.dyndns.org

9 21

[slime-devel] repl history navigation and M-r
by Attila Lendvai 13 Jul '07

13 Jul '07

a recent checkin to cvs eliminated a very useful (ymmv) feature: M-r and M-s behaved just like C-s when it was sequently pressed more then once. i use that feature more than anything in the repl navigation. was it intentional? -- - 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)

3 11

[slime-devel] error message
by Tamas K Papp 07 Jul '07

07 Jul '07

Hi, If I send a function that generates a warning to the inferior lisp process, slime gives this error message: error in process filter: Wrong number of arguments: (lambda (f startval l) "reduce the list l by the binary function f. Use start value startval (cf MacLennnan p. 396)" (cond ((null l) startval) (t (apply f (list (car l) (reduce f startval (cdr l))))))), 4 For example, if the function is (defun foo (bar) nil) and I press C-c C-c, I get the error message (because of the cmucl warning that bar is not used). Am I doing something wrong? I am a Lisp newbie. Versions: ii cmucl 19d-20061116-1 The CMUCL lisp compiler and development syst ii emacs21 21.4a+1-5 The GNU Emacs editor ii slime 20061201-2 Superior LISP Interaction Mode for Emacs Thanks, Tamas

3 4

[slime-devel] How would you like 2 Million Sites linking to your ad ?
by Vik＠common-lisp.net 27 May '07

27 May '07

Discover the power of the Blog Blaster! Brandnew software revolutionizes the power of online advertising -never seen before!- BRAND NEW FOR MARCH 2007! How would you like 2 Million Sites linking to your ad ? Weblog or blog population is exploding around the world, resembling the growth of e-mail users in the 1990s. Post your ads where people read them! - What if you could place your ad on all these sites ? Right, that would mean you would have millions of sites linking to your ad - and my idea actually works. I have developed a software that automatically places your ad on millions of blogs. You will receive thousands of targeted hits to your website as Blog Blaster places your ad on blogs that match your ad's category. This method has never been released to the public before. Very few, if anyone has implemented this For full details please read the attached .html file Unsubscibe: Please read the attached .txt file

1 0

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

25 May '07

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1135 slime/ChangeLog:1.1136 --- slime/ChangeLog:1.1135 Wed May 23 10:26:02 2007 +++ slime/ChangeLog Thu May 24 15:23:24 2007 @@ -1,3 +1,18 @@ +2007-05-24 Tobias C. Rittweiler <tcr(a)freebits.de> + + * swank.lisp: Fixed regression in completion: "swank[TAB]" would + previously be completed to "swank-backend:"; "get-internal[TAB]" + would be completed to "get-internal-r-time" (instead of simply + "get-internal-r"); and "custom:*comp[TAB]" would be completed to + "custom:*compiled-" on CLISP, even though there's a + "custom:*complile-". + + Thanks to Ken Causey for helping me find the first two. + + (completions): Revert changes from 2007-05-11. + (longest-compound-prefix): Fixed to properly generate a compound + _prefix_. + 2007-05-23 Marco Baringer <mb(a)bese.it> * slime.el (def-slime-selector-method): Allow the selector body to @@ -6,7 +21,7 @@ choosing d when there are no debugger buffers) can simply display a message. - Fix handing of auto-flushing on sbcl: + Fix handling of auto-flushing on sbcl: * swank-sbcl.lisp (*auto-flush-interval*): New variable controlling how often streams are flushed.

1 0

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

24 May '07

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1133 slime/ChangeLog:1.1135 --- slime/ChangeLog:1.1133 Thu May 17 12:52:31 2007 +++ slime/ChangeLog Wed May 23 10:26:02 2007 @@ -1,3 +1,21 @@ +2007-05-23 Marco Baringer <mb(a)bese.it> + + * slime.el (def-slime-selector-method): Allow the selector body to + not return a buffer. This means that, instead of being to forced + to signal an error when a choosen buffer can't be found (like + choosing d when there are no debugger buffers) can simply display + a message. + + Fix handing of auto-flushing on sbcl: + + * swank-sbcl.lisp (*auto-flush-interval*): New variable + controlling how often streams are flushed. + (*auto-flush-lock*): New lock guarding access to the shared + variable *auto-flush-streams*. + (make-stream-interactive): Wrapped access to *auto-flush-streams* + in a call-with-recursive-lock-held. + (flush-streams): Wrapped in call-with-recursive-lock-held. + 2007-05-17 Martin Simmons <martin(a)lispworks.com> * swank-lispworks.lisp (lispworks-inspect): Fix hanging caused by

1 0

[slime-devel] Keyboard shortcut mechanism for custom code expanders.
by Vladimir Sedach 23 May '07

23 May '07

Hello, As a result of many long hours spent hacking ParenScript code, the idea for something like "C-c ret but with js:js instead of macroexpand-1" came up. Since ParenScript itself has nothing to do with Slime, and this feature is probably useful for many similar systems, I thought I might as well make this a general facility where you can just add the "expanders" you need in your .emacs. Code is attached (no diffs since I didn't have to change anything). Vladimir

1 1