slime-devel April 2007

slime-devel@common-lisp.net

36 participants
45 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 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] fix for C-c C-c in ecl
by Dustin Long 17 May '07

17 May '07

Hi, Attached is a patch that unbreaks slime-compile-defun in ECL. Without it, the compiler seems to succeed but doesn't actually compile any of the code.

2 2

[slime-devel] wrapping a non-LISP prompt for use by SLIME
by Joe Corneli 30 Apr '07

30 Apr '07

Hi, I have been contributing some work to the Monster Mountain project, http://code.google.com/p/mmtn/ -- which is nominally a Lisp-based MUD, but is, more generally, a Lisp-based application server. One of the things that it currently features is a "multi-user Lisp", with login via netcat. In particular, it largely solves a problem I had brought up on this mailing list in 2006 -- http://common-lisp.net/pipermail/slime-devel/2006-June/005033.html I am now curious about what I think should be a rather simple problem, which is, providing a SLIME connection to this prompt. Schematically, what I envision is: remote server -runs-> LISP 1 LISP 1 -runs-> Monster Mountain remote server -runs-> LISP 2 LISP 2 -runs-> SWANK local Emacs -`slime-connect's over SSH tunnel to-> SWANK SWANK-embedded LISP process -logs in to-> Monster Mountain Result: SLIME interface to Monster Mountain. This looks complicated, but my sense is that it should "just work" if Monster Mountain can provide the "SWANK-embedded LISP process" with the right stuff. I will probably have to ask some additional questions (probably not here) to figure out how to get LISP to connect to Monster Mountain (as above, currently that is done in the shell with netcat), but for this list my question is: what should the interface of the Monster Mountain server look like to its LISP client in order for SLIME to be happy? (My intuition is that it should roughly look like we are in a "virtual package", whatever that would mean.)

1 0

[slime-devel] RFC for completion behaviour
by Tobias C. Rittweiler 28 Apr '07

28 Apr '07

Hi Slime-hackers, Two issues related to how completion should behave: a) As of now, completing on "asdf::" or "asdf::foo" means that it's tried to find any (or the respective) symbols within #<PACKAGE "ASDF"> that is _accessible_. However, this includes all those symbols that are inherited from other packages, including :CL, as most packages include it. If you're looking for a symbol that you know is _internal_ to some package, you're forced to search through (possibly) quite a mess. So what do you think, to change the completion code to only try to match against symbols _internal_ to #<PACKAGE "ASDF"> in the above case? The downside is that if you've got a package :A that uses some internal packages :B and :C for internal code structure purpose, you won't be able to find the symbols in these internal packages. So if people want the new bevahiour, I'd implement it in a way that is has to be explicitely enabled by setting some global value. What's your opinion on this? b) Slime's standard completion function `SLIME-COMPLETE-SYMBOL*' (i.e. the one that is used at the REPL, for instance) completes "asdf:*Com" to "asdf:*COMPILE-FILE--BEHAVIOUR*", where point is at the end of the completion. (As opposed to `SLIME-SIMPLE-COMPLETE-SYMBOL', which would complete it to "asdf:*COMPILE-FILE-".) Traditionally, the point has been set to the place between the two dashes ("asdf:*COMPILE-FILE-|-BEHAVIOUR*", where "|" is supposed to mean the cursor.) It doesn't anymore, rendering that kind of completion pretty much b0rked. I'd like to restore the traditional behaviour. Comments? -T.

7 13

[slime-devel] slime-complete-form extra parenthesis
by Mac Chan 28 Apr '07

28 Apr '07

I use slime-complete-form a lot. However, like many who uses slime, I also have paredit-mode enabled. Is there a way to instruct slime-complete-form not to insert extra close parenthesis at the end? (with-open-file _) => C-c C-s slime-complete-form => (with-open-file _(stream filespec :direction direction :element-type element-type :if-exists if-exists :if-does-not-exist if-does-not-exist :external-format external-format) body...)) ;; <-- extra ) Thanks, -- Mac

1 0

[slime-devel] Inserting eval results in the current buffer
by Nikodemus Siivola 27 Apr '07

27 Apr '07

I submit that the current behaviour of <prefix> C-x C-e is not very useful. It is probably almost ideal for <prefix> C-c : -- eg. for creating constants with one-liners. This is what I use in lieu of it, and what might be good for Slime proper too. (defun ns:scan-forward (stop-after stop-before) (do () ((or (eql (char-after) stop-before) (eql (char-before) stop-after))) (forward-char))) (defun ns:comment-at-eol () (let ((newline (string-to-char "\n")) (comment (string-to-char ";"))) (ns:scan-forward comment newline) (unless (eql newline (char-after)) (kill-line)) (unless (eql comment (char-before)) (insert " ;"))) (insert " ")) (defun ns:eval-in-lisp-insert-comment () (interactive) (lexical-let ((current-buffer (current-buffer))) (slime-eval-with-transcript `(swank:interactive-eval ,(slime-last-expression)) `(lambda (value) (with-current-buffer ,current-buffer (ns:comment-at-eol) (insert (format "%s" value))))))) Cheers, -- Nikodemus

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel April 2007