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

[slime-devel] SLIME and Lispworks?
by Alain.Picard＠memetrics.com 27 Nov '03

27 Nov '03

Dear SLIME developers (hi Luke!) Well, ILISP has been annoying me _SO_ much recently I figured it may finally be time to do something about it; then I stumbled on this project. I realize (from reading your sources so far) that you're focussing on CMUCL and SBCL; however, if the intent is to try to make the protocol sufficiently general/portable to other Lisps, I hereby volunteer my services as Lispworks user/tester/debugger (and even, initially) porter of whatever LW specific code needs to be written to get SLIME going on LW. I can't promise I have a lot of time to devote to this, so I'll be happy to pass the ball on to whoever wants to take this up next, but one is greater than zero, so I'm willing to give this a go, if the concensus of this list is that this is a) feasible b) a good idea So let me know your thoughts. (I won't be offended if you think such an effort is undesirable or premature, so feel free to speak your collective minds). yours, --Alain Picard

3 12

[slime-devel] REPL mode
by Helmut Eller 02 Nov '03

02 Nov '03

Hi, I've committed the beginnings of a comint-less REPL. Here are some thoughts. This is a proof of concept, to see if our own REPL is actually better than the (not-so-) inferior-lisp mode. The REPL is activated in the in idle-state and shares the buffer with the other (redirected) output. Some markers track the prompt, the user input, and the beginning of the output. The current design doesn't maintain any state on the Lisp side (we probably should do that, e.g., for things like *, **, *** etc.). Some not so nice things about the new REPL: - since I didn't use comint I had to implement the history management myself. - prompting is triggered by the activation event of the idle state. This means the prompt is printed before we can print the result and we have to go back and insert the result before the prompt. Also we have to check on every idle-state activation event, if we actually need insert a prompt (to avoid many unneeded prompts). - slime-space can produce output and cause a new prompt. This can happen when CMUCL emits warnings during the first coercion a symbol to a function. There is currently no good input handling, e.g, when the Lisp side calls read-char on the redirected input stream, Emacs just reads a line from the minibuffer. My plan was to switch the keymap in the repl buffer when the Lisp side request input. The other keymap doesn't behave like a repl, but send the input more or less uninterpreted to the Lisp side. Not sure how to implement this though. Since I'm not using the repl all that much I'm not sure if it is worth the trouble. There are also problems with output buffering, e.g., when you evaluate (labels ((foo () (foo) t)) (foo)) in the listener, CMUCL puts you in the (tty-) debugger, but you can't see it because the output is buffered somewhere. The nicest thing about this repl is the integration with our debugger. The ugliest thing is the complexity that is needed for better input redirection. Helmut.

2 2

[slime-devel] Automatically remove *Completions* buffer
by Paolo Amoroso 31 Oct '03

31 Oct '03

After doing symbol completion with M-TAB in *inferior-lisp*, the *Completions* buffer remains open if it had previously been activated. Is it possible to make *Completions* disappear as soon as a unique symbol is selected? Paolo -- Paolo Amoroso <amoroso(a)mclink.it>

3 4

[slime-devel] Does SLIME change editor features significantly?
by Martin Stone Davis 31 Oct '03

31 Oct '03

Total newbie here. I have ILISP and I understand that SLIME is for making it easier for Emacs to interact with 3rd party Lisp interpreters. But does/will it also improve on Emacs-Lisp mode? For example, here are some things I'm looking for: * automatic re-indentation (so that if I cut paste something it automatically adjusts the indentation) * "better" keyboard keyboard mappings for movement/selection Without getting into too much detail, I first just wanna know if the above is even within the scope of SLIME. Thanks, -Martin

2 1

[slime-devel] More SLIME wish items
by Raymond Toy 30 Oct '03

30 Oct '03

Since Luke has been very good about getting my wish items into slime, here, I think, is the last one that really prevents me from switching completely to slime from ilisp. In ilisp, if you're in the debugger, pressing C-d pops one level of the debugger. In slime, I press C-d all the time, but cmucl sees a literal C-d and thinks end-of-file. Fortunately, cmucl doesn't exit. And, since we're wishing right now, here's another feature from ilisp that I like and use once in a while. Comes in handy when you're testing different versions of cmucl, or comparing how different lisps behave. Ilisp allows several buffers running at the same time. Each buffer is running a different lisp instance. This can be the same lisp or a different lisp implementation altogether. Anyway, slime rocks! Ray

4 6

[slime-devel] slime-quit errors
by Paolo Amoroso 29 Oct '03

29 Oct '03

When I issue the `slime-quit' command (bound to C-c ESC g) from *inferior-lisp*, I usually get this error in the minibuffer: Symbol's function definition is void: pp-to-string One time I got this in *inferior-lisp*: * ;; Connection to Emacs lost. ;; [End-of-File on #<Stream for descriptor 6>] and this in a separate buffer: You have encountered a bug in SLIME. The communication state machine received an event that was illegal for its current state, which means that the communication between Emacs and Lisp has lost synchronization. The connection to Lisp has therefore been closed. You can open a fresh connection with `M-x slime'. Please report this problem to your friendly neighbourhood SLIME hacker, or the mailing list at slime-devel(a)common-lisp.net. Please include in your report: A description of what you were doing when the problem occured, the version of SLIME, Emacs, and Lisp that you are using, the Lisp backtrace, if one was printed, and the information printed below: The event was: (:emacs-quit) The state stack was: (slime-idle-state) I can't remember exactly what I was doing, but I was evaluating very simple forms and checking a few SLIME commands such as `lisp-describe-sym'. Previously, I had exited a SLIME session with `(quit)' *inferior-lisp*, and then started a new one with `M-x slime'. My setup is: Debian Woody, GNU Emacs 20.7, CMUCL 18e and SLIME CVS sources updated half a dozen hours ago. Paolo -- Paolo Amoroso <amoroso(a)mclink.it>

2 3

[slime-devel] Abnormal exit with code 256
by Paolo Amoroso 29 Oct '03

29 Oct '03

When I quit CMUCL from *inferior-lisp* with `(quit)' I get the following message in the buffer: Process inferior-lisp finished and these messages in the echo area/minibuffer: (Inferior Lisp:no process Inf-Slime[not connected]) Lisp connection closed:exited abnormally with code 256^J Is this the expected behavior? My setup is: Debian Woody, GNU Emacs 20.7, CMUCL 18e, SLIME CVS sources updated half a dozen hours ago. Paolo P.S. I almost forgot: kudos! -- Paolo Amoroso <amoroso(a)mclink.it>

2 3

[slime-devel] not-so-inferior-slime-mode, backhackattack-1
by Luke Gorrie 28 Oct '03

28 Oct '03

Ahoy, Did some improvements to the inferior-slime-mode based on helpful feedback: now it's careful about preserving history with multi-line input, and it also indents it as Lisp code. There's also a command on C-RET that closes all your open parenthesis and sends the input to Lisp. More significantly, I started on The Great Backend Refactoring. This is ultra-disruptive, so I (gag) made a branch: backhackattack-1. The idea is to violently hack things into shape, initially only with the CMUCL backend, and then, only when it's right, update the other backends too. Meanwhile normal use/development can continue on the trunk. The hope is to only be branched for less than a week. So far all I've done is split swank.lisp and swank-cmucl.lisp into separate packages, so that the interface is more explicit. It currently gets through the test suite. The code looks pretty much like a pair of Siamese twins separated by a chainsaw -- lots of internal stuff shared all around the place with no logical division, but with the connections laid bare for the eye to see. The next step is to jumble things around so that the backend implements a small and well-defined interface, and swank.lisp exports as little as possible to support it. AFAICS the best general strategy is moving code from the backend into swank.lisp. Anyone who wants to get muddy is welcome to join in :-) For the callbacks, I'm currently defining the symbols and placeholder-functions in the SWANK package. Then swank-cmucl.lisp contains a bunch of "(defun swank:foobar ..)" forms to properly define the callbacks. May or may not be a good idea. Cheers, Luke

2 3

[slime-devel] slime messing with my window configuration
by Andreas Fuchs 26 Oct '03

26 Oct '03

hi, I often use slime as I used ILISP: have two windows in a frame, split vertically, one containing the lisp source, the other containing the *inferior-lisp*. When slime pops up a buffer, e.g. a debug buffer and I exit it, slime closes the window with my code in it and I am left with just an *inferior-lisp* buffer in the frame. Although I'm used to typing <restart> C-x 3 C-x b RET (luckily the last "code" buffer is the default) now, it's pretty tedious. Other than that, I'm very happy with SLIME right now. Great work, guys. Thanks, -- Andreas Fuchs, <asf(a)acm.org>, asf(a)jabber.at, antifuchs

2 2

[slime-devel] SBCL backend fix
by Luke Gorrie 23 Oct '03

23 Oct '03

Hi, I updated the SBCL backend to use a character stream to match the swank.lisp changes, which fixes a problem reported by Raymond Wiker on comp.lang.lisp. It doesn't look like the OpenMCL backend needs a similar update, but I'm not certain. For me the symptom of this problem includes totally hanging Emacs. That's no good, I'm looking for the cause. Cheers, Luke

3 3