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

[slime-devel] loopback interface
by Robert Brown 04 Oct '05

04 Oct '05

Recently, I've been running a Lisp-based server on a batch scheduling system. The scheduler starts up my server on an available machine and then I'd like to connect to it with Slime. I've noticed two things: 1. The code in swank.lisp listens on port 127.0.0.1 <http://127.0.0.1>, which means I cannot connect to my Lisp server from a remote machine. I must log in to the host it's running on and then specify "localhost" when I execute slime-connect in Emacs. If swank is running on host "foo", why doesn't it bind its listening socket with foo's address? 2. I modified swank.lisp so the server code binds its listening connection socket with foo's address. Now I can connect from a remote machine. Is there any convenient way to send whole files across the Slime connection? The Lisp running the swank server has no NFS access to the machine I'm running Emacs on. I'd like to be able to edit files on the Emacs side and send then whole to the Lisp running swank. bob

5 5

[slime-devel] SLIME48: a Swank back end in Scheme48
by Taylor Campbell 04 Oct '05

04 Oct '05

About a month ago, as I was thinking about building a comprehensive development environment for Scheme (& Scheme48 in particular), akin to SLIME, the notion occurred to me that Scheme48 might actually provide the necessary facilities for a realistic Swank back end (as compared to the mostly toy back end Helmut Eller sent here a while ago). So I started working on it a bit in small increments, and pretty soon Emacs was successfully talking to it over TCP to evaluate simple REPL expressions. Last week I implemented SLDB support, after rewriting it from scratch once my initial prototype worked; I spent the whole weekend fixing a really obscure bug involving threads, continuations, & DYNAMIC-WIND; and just today I've gotten it into an almost usable state for REPL work (though not file & module loading & such yet). Currently, I'm not using any source control yet, and I haven't released the code anywhere, but Marco Baringer and several others recommended that I simply add the Scheme48 back end to the main SLIME CVS source repository. If everyone relevant would be OK with this, I'd like to do it, but I see one potential problem with it, assuming that no one would object to including Scheme code in SLIME: I've organized my Scheme48 back end into about a dozen different files, which is pretty different from the existing organization of SLIME code (one monolithic file for the Emacs side; one monolithic file for the bulk of the CL side; one monolithic file for each back end). Would this bother anyone? (I intend, by the way, not to change the Emacs side of SLIME to add anything Scheme-specific; if anything, I'd want only to make slime.el work better with both Scheme & CL -- e.g., Marco Baringer just kindly committed a change I suggested that makes the definition locator code look for definitions where a sequence of parentheses might precede the name being defined, such as in (DEFINE (FOO X) ...) to define FOO in Scheme, or (DEFSTRUCT (BAR ...) ...) to define a BAR structure in CL. There are a few other minor changes like these that would be convenient for Scheme48's back end, but which would not get in the way of the CL back ends, too.) Obligatorily, here's some SLIME48 porn, by the way: <http://www.bloodandcoffee.net/campbell/slime48-sldb-porn.png> (The CL-USER prompt and the mention of a COMMON-LISP-USER package are due to slime.el's hard-coded initial package of COMMON-LISP-USER -- another small change I'd like to make is to allow customization of the initial package. (The temporary solution was for me just to define a COMMON-LISP-USER package in Scheme48, of course.))

12 33

[slime-devel] presentations/repl history problem
by Alan Ruttenberg 03 Oct '05

03 Oct '05

Somewhere in the last ~2 months, a change I made was (searching for the diplomatic word here...) "regressed". The symptom is that when I bring back something from the repl history (via meta-p) that contains a presentation, the presentation is no longer in the right style, and return sends the presentation string rather than for to evaluate to the object, causing an error. I spent a reasonable amount of time this morning looking for the bug but things have changed enough that I can't understand what's going on well enough to find it. Could someone who is familiar with the relevant changes to the presentation system please review this problem and suggest a fix? The presentation stuff, at least on the emacs side, could use some documentation at this point. What are the features? How are they implemented? Thanks, Alan 2005-08-10 Alan Ruttenberg <alanr-l(a)mumble.net> * slime.el move slime-repl-add-to-input-history to slime-repl- send-input so we can see the presentations we copied to input when we reuse history rather than #.(blah...)

1 0

[slime-devel] communication style
by Robert Brown 03 Oct '05

03 Oct '05

Please document the NIL setting of SWANK:*COMMUNICATION-STYLE*. Better yet, select its behavior with a new keyword value, something like :SERVER-LOOP. Yesterday, I found I needed this setting as was I trying to get Slime working to a non-threaded SBCL running in an environment where its standard input is basically /dev/null. Thanks very much for Slime. It's fabulous. bob

1 0

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

01 Oct '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.790 slime/ChangeLog:1.791 --- slime/ChangeLog:1.790 Thu Sep 29 07:16:19 2005 +++ slime/ChangeLog Sat Oct 1 14:00:27 2005 @@ -1,3 +1,8 @@ +2005-10-01 Juho Snellman <jsnell(a)iki.fi> + * swank-backend (*gray-stream-symbols*): Add :STREAM-LINE-LENGTH + to *GRAY-STREAM-SYMBOLS* on implementations that support this + extension to gray streams. Reported by Matthew D Swank. + 2005-09-29 Luke Gorrie <luke(a)synap.se> * swank-scheme48: Removed due to excessive whining.

1 0

[slime-devel] nit: zap (setq it choice-to-lambda) from `slime-presentation-menu'
by jpw＠gnu.org 01 Oct '05

01 Oct '05

Howdy, Nothing uses it. I guess it is a stray debugging/development artifact. How about zapping it ? 2005-10-01 John Paul Wallington <jpw(a)pobox.com> * slime.el (slime-presentation-menu): Don't set free variable `it' to value of `choice-to-lambda'. --- slime.el 01 Oct 2005 13:47:58 +0100 1.552 +++ slime.el 01 Oct 2005 18:49:44 +0100 @@ -3118,7 +3118,6 @@ (error "No presentation at event position")) (let ((menu (slime-menu-choices-for-presentation presentation from to choice-to-lambda))) - (setq it choice-to-lambda) (let ((choice (x-popup-menu event menu))) (when choice (call-interactively (gethash choice choice-to-lambda)))))))))

1 0

[slime-devel] error in swank after upgrading to sbcl 0.9.5 (linux x86)
by Matthew D Swank 01 Oct '05

01 Oct '05

When I am alerted to a symbol conflict: USE-PACKAGE #<PACKAGE "UTIL"> causes name-conflicts in #<PACKAGE "COMMON-LISP-USER"> between the following symbols: UTIL:APPLY, APPLY [Condition of type SB-INT:NAME-CONFLICT] See also: Common Lisp Hyperspec, 11.1.1.2.5 [section] Restarts: 0: [RESOLVE-CONFLICT] Resolve conflict. 1: [ABORT-REQUEST] Abort handling SLIME request. 2: [TERMINATE-THREAD] Terminate this thread (#<THREAD "repl-thread" {9167109}>) and pick 0, I get the following error: There is no applicable method for the generic function #<STANDARD-GENERIC-FUNCTION STREAM-LINE-LENGTH (1)> when called with arguments (#<SWANK-BACKEND::SLIME-INPUT-STREAM {915D6B1}>). [Condition of type SIMPLE-ERROR] Restarts: 0: [ABORT] Return to sldb level 1. 1: [ABORT-REQUEST] Abort handling SLIME request. 2: [TERMINATE-THREAD] Terminate this thread (#<THREAD "repl-thread" {9167109}>) Backtrace: 0: ((SB-PCL::FAST-METHOD NO-APPLICABLE-METHOD (T)) #<unavailable argument> #<unavailable argument> #<STANDARD-GENERIC-FUNCTION STREAM-LINE-LENGTH (1)> (#<SWANK-BACKEND::SLIME-INPUT-STREAM {915D6B1}>)) ... full error attached Matt -- "You do not really understand something unless you can explain it to your grandmother." — Albert Einstein. There is no applicable method for the generic function #<STANDARD-GENERIC-FUNCTION STREAM-LINE-LENGTH (1)> when called with arguments (#<SWANK-BACKEND::SLIME-INPUT-STREAM {915D6B1}>). [Condition of type SIMPLE-ERROR] Restarts: 0: [ABORT] Return to sldb level 1. 1: [ABORT-REQUEST] Abort handling SLIME request. 2: [TERMINATE-THREAD] Terminate this thread (#<THREAD "repl-thread" {9167109}>) Backtrace: 0: ((SB-PCL::FAST-METHOD NO-APPLICABLE-METHOD (T)) #<unavailable argument> #<unavailable argument> #<STANDARD-GENERIC-FUNCTION STREAM-LINE-LENGTH (1)> (#<SWANK-BACKEND::SLIME-INPUT-STREAM {915D6B1}>)) 1: ((SB-PCL::FAST-METHOD NO-APPLICABLE-METHOD (T)) #<unavailable argument> #<unavailable argument> #<STANDARD-GENERIC-FUNCTION STREAM-LINE-LENGTH (1)> (#<SWANK-BACKEND::SLIME-INPUT-STREAM {915D6B1}>)) 2: (SB-IMPL::TWO-WAY-MISC #<TWO-WAY-STREAM :INPUT-STREAM #<SWANK-BACKEND::SLIME-INPUT-STREAM {915D6B1}> :OUTPUT-STREAM #<SB-SYS:FD-STREAM for "a constant string" {9028109}>> :LINE-LENGTH NIL NIL) 3: (SB-PRETTY::MAKE-PRETTY-STREAM #<TWO-WAY-STREAM :INPUT-STREAM #<SWANK-BACKEND::SLIME-INPUT-STREAM {915D6B1}> :OUTPUT-STREAM #<SB-SYS:FD-STREAM for "a constant string" {9028109}>>) 4: (SB-FORMAT::INTERPRET-FORMAT-LOGICAL-BLOCK #<TWO-WAY-STREAM :INPUT-STREAM #<SWANK-BACKEND::SLIME-INPUT-STREAM {915D6B1}> :OUTPUT-STREAM #<SB-SYS:FD-STREAM for "a constant string" {9028109}>> ("COMMON-LISP-USER" ((1 1 UTIL:APPLY) (1 2 APPLY))) ("COMMON-LISP-USER" ((1 1 UTIL:APPLY) (1 2 APPLY))) "" NIL ("Select " #<> "a " #<> "symbol " #<> "to " #<> "be " #<> ...) "" T) 5: (SB-FORMAT::<-FORMAT-DIRECTIVE-INTERPRETER #<TWO-WAY-STREAM :INPUT-STREAM #<SWANK-BACKEND::SLIME-INPUT-STREAM {915D6B1}> :OUTPUT-STREAM #<SB-SYS:FD-STREAM for "a constant string" {9028109}>> #<~@<> ("Select a symbol to be made accessible in " #<~ > " package " #<~A> ":" #<~2I> #<~@:_> #<~{> #<~{> #<~V,' D> ...) ("COMMON-LISP-USER" ((1 1 UTIL:APPLY) (1 2 APPLY))) ("COMMON-LISP-USER" ((1 1 UTIL:APPLY) (1 2 APPLY)))) 6: (SB-FORMAT::INTERPRET-DIRECTIVE-LIST #<TWO-WAY-STREAM :INPUT-STREAM #<SWANK-BACKEND::SLIME-INPUT-STREAM {915D6B1}> :OUTPUT-STREAM #<SB-SYS:FD-STREAM for "a constant string" {9028109}>> (#<~@<> "Select a symbol to be made accessible in " #<~ > " package " #<~A> ":" #<~2I> #<~@:_> #<~{> #<~{> ...) ("COMMON-LISP-USER" ((1 1 UTIL:APPLY) (1 2 APPLY))) ("COMMON-LISP-USER" ((1 1 UTIL:APPLY) (1 2 APPLY)))) 7: (SB-FORMAT::%FORMAT #<TWO-WAY-STREAM :INPUT-STREAM #<SWANK-BACKEND::SLIME-INPUT-STREAM {915D6B1}> :OUTPUT-STREAM #<SB-SYS:FD-STREAM for "a constant string" {9028109}>> "~&~@<Select a symbol to be made accessible in ~ package ~A:~2I~@:_~{~{~V,' D. ~S~}~@:_~}~@:>" ("COMMON-LISP-USER" ((1 1 UTIL:APPLY) (1 2 APPLY))) ("COMMON-LISP-USER" ((1 1 UTIL:APPLY) (1 2 APPLY)))) 8: (FORMAT #<TWO-WAY-STREAM :INPUT-STREAM #<SWANK-BACKEND::SLIME-INPUT-STREAM {915D6B1}> :OUTPUT-STREAM #<SB-SYS:FD-STREAM for "a constant string" {9028109}>> "~&~@<Select a symbol to be made accessible in ~ package ~A:~2I~@:_~{~{~V,' D. ~S~}~@:_~}~@:>") 9: ((LAMBDA NIL)) 10: (INVOKE-RESTART-INTERACTIVELY #<RESTART SB-INT:RESOLVE-CONFLICT {AD30879}>) 11: (SB-INT:EVAL-IN-LEXENV (SWANK:INVOKE-NTH-RESTART-FOR-EMACS 1 0) #<NULL-LEXENV>) 12: ((LAMBDA NIL)) 13: ((SB-PCL::FAST-METHOD SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK (T T)) #<unused argument> #<unused argument> #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA NIL) {AE95AA5}>) 14: (SWANK::SLDB-LOOP 1) 15: ((SB-PCL::FAST-METHOD SWANK-BACKEND:CALL-WITH-DEBUGGING-ENVIRONMENT (T)) #<unused argument> #<unused argument> #<FUNCTION (LAMBDA NIL) {B271F15}>) 16: (SWANK::CALL-WITH-BINDINGS ((*PRINT-PRETTY*) (*PRINT-LEVEL* . 4) (*PRINT-LENGTH* . 10) (*PRINT-CIRCLE* . T) (*PRINT-READABLY*) (*PRINT-PPRINT-DISPATCH* . #<SB-PRETTY:PPRINT-DISPATCH-TABLE {B314759}>) (*PRINT-GENSYM* . T) (*PRINT-BASE* . 10) (*PRINT-RADIX*) (*PRINT-ARRAY* . T) ...) #<FUNCTION (LAMBDA NIL) {B271ED5}>) 17: (SWANK::DEBUG-IN-EMACS #<SB-INT:NAME-CONFLICT {AD30929}>) 18: (INVOKE-DEBUGGER #<SB-INT:NAME-CONFLICT {AD30929}>) 19: (ERROR #<SB-INT:NAME-CONFLICT {AD30929}>) 20: (SB-INT:NAME-CONFLICT #<PACKAGE "COMMON-LISP-USER"> USE-PACKAGE #<PACKAGE "UTIL">) 21: (USE-PACKAGE :UTIL #<PACKAGE "COMMON-LISP-USER">) 22: (SB-INT:EVAL-IN-LEXENV (USE-PACKAGE :UTIL) #<NULL-LEXENV>) 23: (SWANK::EVAL-REGION "(use-package :util) " T) 24: ((LAMBDA NIL)) 25: ((SB-PCL::FAST-METHOD SWANK-BACKEND:CALL-WITH-SYNTAX-HOOKS (T)) #<unused argument> #<unused argument> #<CLOSURE (LAMBDA NIL) {AD30425}>) 26: (SWANK::CALL-WITH-BUFFER-SYNTAX #<CLOSURE (LAMBDA NIL) {AD30425}>) 27: (SB-INT:EVAL-IN-LEXENV (SWANK:LISTENER-EVAL "(use-package :util) ") #<NULL-LEXENV>) 28: ((LAMBDA NIL)) 29: ((SB-PCL::FAST-METHOD SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK (T T)) #<unused argument> #<unused argument> #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA NIL) {AD2BC4D}>) 30: ((LAMBDA NIL)) 31: ((LAMBDA NIL)) 32: (SWANK::CALL-WITH-REDIRECTED-IO #<SWANK::CONNECTION {90263F1}> #<CLOSURE (LAMBDA NIL) {AD2BB2D}>) 33: (SWANK::CALL-WITH-CONNECTION #<SWANK::CONNECTION {90263F1}> #<FUNCTION (LAMBDA NIL) {B2332FD}>) 34: (SWANK::HANDLE-REQUEST #<SWANK::CONNECTION {90263F1}>) 35: ((LAMBDA NIL)) 36: ((LAMBDA NIL)) 37: ((LAMBDA NIL)) 38: (SWANK::CALL-WITH-REDIRECTED-IO #<SWANK::CONNECTION {90263F1}> #<CLOSURE (LAMBDA NIL) {917808D}>) 39: (SWANK::CALL-WITH-CONNECTION #<SWANK::CONNECTION {90263F1}> #<CLOSURE (LAMBDA NIL) {917807D}>) 40: (SWANK::CALL-WITH-BINDINGS NIL #<CLOSURE (LAMBDA NIL) {917805D}>) 41: ((LAMBDA NIL)) 42: ("foreign function: call_into_lisp") 43: ("foreign function: funcall0") 44: ("foreign function: new_thread_trampoline") 45: ("foreign function: #xB7FC03B0")

2 2

[slime-devel] change current indentation?
by Maurice 01 Oct '05

01 Oct '05

Hi, is there a way to change the indentation for some specific lines? For example this comes up using the default indentation: (define-event-handler 'events (:key-down (key) (print key)) (:mouse-down (button x y) ...)) And I want it like this: (define-event-handler 'events (:key-down (key) (print key)) (:mouse-down (button x y) ...)) Maybe it's possible to define a key which cycles through the various standard indentations? Thank you.

1 0