From: Zach B. <xa...@xa...> - 2004-11-08 22:00:03
|
I've been trying to use the latest CVS sbcl with the latest CVS slime. I'm not sure when it started, but they don't seem to work together as of today (2004-11-08). To reproduce: 1. Start SLIME with a recent CVS sbcl 2. At the slime repl, type "*features*" At that point, I get a message like "error in process filter: wrong type argument listp," in the minibuffer. (When I try to select it, it disappears, sorry for the imprecision.) There seem to be a number of other ways to trigger a communication breakdown. I have no idea what's up; the only odd thing I noticed was a bare "\226" character in the *slime-events* buffer. I tried two versions of sbcl, one with the :sb-unicode feature enabled and another without. It didn't seem to make a difference. A version of SBCL from last month works fine. Zach |
From: Alexey D. <ade...@co...> - 2004-11-09 03:12:13
|
Hello, Zach Beane <xa...@xa...> writes: > I've been trying to use the latest CVS sbcl with the latest CVS > slime. I'm not sure when it started, but they don't seem to work > together as of today (2004-11-08). > > To reproduce: > > 1. Start SLIME with a recent CVS sbcl > > 2. At the slime repl, type "*features*" > > At that point, I get a message like "error in process filter: wrong > type argument listp," in the minibuffer. (When I try to select it, it > disappears, sorry for the imprecision.) I had the same problem when I updated SBCL to the Unicode version. But for me removing .slime/sbcl*/*.fasl and restarting emacs has solved the problem. Just updated SLIME and SBCL 0.8.16.35 with :SB-UNICODE pass your test here. -- Regards, Alexey Dejneka "Alas, the spheres of truth are less transparent than those of illusion." -- L.E.J. Brouwer |