[slime-devel] Problem running PortableAllegroServe using CMUCL under SLIME
Hi, First, thank you for the great tool! I really enjoy using it. I ran into the following problem, though: 1) Starting SLIME -> CMUCL -> PortableAServe's examples; 2) After some browsing, the PortableAServe prints some messages to the *SLIME-REPL* (IIRC the name) buffer; 3) After that, when I try to evaluate anything in the *SLIME-REPL* buffer, I got something like "This buffer is read-only" in the status bar and the caret moved to the top of the buffer. Cheers, Ivan
Ivan Toshkov <ivan@toshkov.org> writes:
Hi,
First, thank you for the great tool! I really enjoy using it.
I ran into the following problem, though:
1) Starting SLIME -> CMUCL -> PortableAServe's examples;
i've similar had issues (though not this exact problem) with partableaserve's multi-thread-ness and slime's single-thread-at-a-time-ness. You might want to try starting portableaserve for a terminal and using swank:create-swank-server + slime-connect. just don't connect to the same server more than once. -- -Marco Ring the bells that still can ring. Forget your perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen
Today, Ivan Toshkov <ivan@toshkov.org> wrote:
1) Starting SLIME -> CMUCL -> PortableAServe's examples; 2) After some browsing, the PortableAServe prints some messages to the *SLIME-REPL* (IIRC the name) buffer; 3) After that, when I try to evaluate anything in the *SLIME-REPL* buffer, I got something like "This buffer is read-only" in the status bar and the caret moved to the top of the buffer.
I can see that problem without PAserve, too. it seems to be related with output that arrives after the prompt was printed. evaluating something in a slime buffer with C-M-x (or doing anything that causes output) fixes that most of the time. -- Andreas Fuchs, <asf@boikor.net>, asf@jabber.at, antifuchs
andreas fuchs wrote:
Today, Ivan Toshkov <ivan@toshkov.org> wrote:
1) Starting SLIME -> CMUCL -> PortableAServe's examples; 2) After some browsing, the PortableAServe prints some messages to the *SLIME-REPL* (IIRC the name) buffer; 3) After that, when I try to evaluate anything in the *SLIME-REPL* buffer, I got something like "This buffer is read-only" in the status bar and the caret moved to the top of the buffer.
I can see that problem without PAserve, too. it seems to be related with output that arrives after the prompt was printed.
evaluating something in a slime buffer with C-M-x (or doing anything that causes output) fixes that most of the time.
That worked! Thanks.
Ivan Toshkov <ivan@toshkov.org> writes:
I ran into the following problem, though:
1) Starting SLIME -> CMUCL -> PortableAServe's examples; 2) After some browsing, the PortableAServe prints some messages to the *SLIME-REPL* (IIRC the name) buffer; 3) After that, when I try to evaluate anything in the *SLIME-REPL* buffer, I got something like "This buffer is read-only" in the status bar and the caret moved to the top of the buffer.
This is probably a problem with multi-threading caused by mp::startup-idle-and-top-level-loops, but I have to try it myself to see what the problems are. In the meantime you can try to call mp::startup-idle-and-top-level-loops in your .swank.lisp, but debugging will probably not work very well. An older version of SLIME might work better, e.g, the version tagged with SLIME-0-9. Helmut.
participants (4)
-
andreas fuchs -
Helmut Eller -
Ivan Toshkov -
Marco Baringer