[slime-devel] Slime with SBCL 1.0.22 on windows ; pipelined request... (swank:listener-eval "d
I installed slime, and SBCL for windows, and it works fine, except for the REPL. Everything works great until I do something to cause an error, when I do, the debugger fires and gives me my options, and no matter which one I choose, nothing happens. The CL-USER> prompt doesn't come back, it just hangs up, and any thing I type results in it saying "; pipelined request... (swank:listener-eval "d". Is there any way to fix this? This really sucks. I'm sure it's something to do with SBCL because the windows port is experimental, just shooting at the chance of there being a fix for it.
Thanks
-Rayne
On Sun, Dec 21, 2008 at 6:40 PM, Rayne rayne@acidrayne.net wrote:
I installed slime, and SBCL for windows, and it works fine, except for the REPL. Everything works great until I do something to cause an error, when I do, the debugger fires and gives me my options, and no matter which one I choose, nothing happens. The CL-USER> prompt doesn't come back, it just hangs up, and any thing I type results in it saying "; pipelined request... (swank:listener-eval "d". Is there any way to fix this? This really sucks. I'm sure it's something to do with SBCL because the windows port is experimental, just shooting at the chance of there being a fix for it.
Confirmed under Windows XP, SBCL 1.0.22, and the newest slime (2008-12-09). I don't know a fix, but somehow I don't remember this being a problem in the past, so this could be a regression (or my memory is just bad).
Rayne wrote:
I installed slime, and SBCL for windows, and it works fine, except for the REPL. Everything works great until I do something to cause an error, when I do, the debugger fires and gives me my options, and no matter which one I choose, nothing happens. The CL-USER> prompt doesn't come back, it just hangs up, and any thing I type results in it saying "; pipelined request... (swank:listener-eval "d". Is there any way to fix this? This really sucks. I'm sure it's something to do with SBCL because the windows port is experimental, just shooting at the chance of there being a fix for it.
Thanks
-Rayne
Same here. No matter what restart / abort I select, it hangs. e.g. after evaluating...
(symbol-not-defined)
...and selecting...
1: [ABORT] Return to SLIME's top level.
I'm using
Slime CVS (downloaded today) SBCL 1.0.22 XEmacs 21.4.21 Windows XP
My init.el looks like this:
(setq inferior-lisp-program "E:/dev/sbcl/1.0.22/sbcl.exe") (add-to-list 'load-path "E:/dev/slime-2008-12-22/") (require 'slime)
SBCL doesn't hang when using it directly.
Thanks,
WalterGR
* Rayne [2008-12-22 03:40+0100] writes:
I installed slime, and SBCL for windows, and it works fine, except for the REPL. Everything works great until I do something to cause an error, when I do, the debugger fires and gives me my options, and no matter which one I choose, nothing happens. The CL-USER> prompt doesn't come back, it just hangs up, and any thing I type results in it saying "; pipelined request... (swank:listener-eval "d". Is there any way to fix this? This really sucks. I'm sure it's something to do with SBCL because the windows port is experimental, just shooting at the chance of there being a fix for it.
This sounds like this problem: gmane.lisp.slime.devel/7991
Scroll down to the workaround.
Summary: it's a problem with SBCL/Windows/READ-CHAR-NO-HANG/socket-streams.
We could work around that in SLIME but it would clearly be better if the bug would be fixed in SBCL.
Helmut.
Helmut Eller wrote:
- Rayne [2008-12-22 03:40+0100] writes:
I installed slime, and SBCL for windows, and it works fine, except for the REPL. Everything works great until I do something to cause an error, when I do, the debugger fires and gives me my options, and no matter which one I choose, nothing happens. The CL-USER> prompt doesn't come back, it just hangs up, and any thing I type results in it saying "; pipelined request... (swank:listener-eval "d". Is there any way to fix this? This really sucks. I'm sure it's something to do with SBCL because the windows port is experimental, just shooting at the chance of there being a fix for it.
This sounds like this problem: gmane.lisp.slime.devel/7991
Scroll down to the workaround.
That "fixed" it. Thanks!
Summary: it's a problem with SBCL/Windows/READ-CHAR-NO-HANG/socket-streams.
We could work around that in SLIME but it would clearly be better if the bug would be fixed in SBCL.
Indeed.
Walter
On Tue, Dec 23, 2008 at 12:13 AM, Helmut Eller heller@common-lisp.net wrote:
Summary: it's a problem with SBCL/Windows/READ-CHAR-NO-HANG/socket-streams.
We could work around that in SLIME but it would clearly be better if the bug would be fixed in SBCL.
No disagreement there. However, considering that no-one is actively working on the Windows port right now, and that READ-CHAR-NO-HANG has AFAIK always behaved like this on SBCL/Windows, I think the practical solution is to work around it.
(If someone is knowledgeable about Windows, I would be more than happy to point them to the relevant bits in SBCL code, and merge any fix they come up with, though.)
Cheers,
-- Nikodemus
-
Elliott Slaughter -
Helmut Eller -
Nikodemus Siivola -
Rayne -
Walter GR