Prev: Does slime introduce errors into cmucl?
Next: Currying and Cleave in Common Lisp
From: Norbert_Paul on 31 Mar 2010 02:28
Raymond Toy wrote:
> What swank:*communication-style* do you use? I think, but I'm not sure,
> that anything other than :fd-handler is suspect. CMUCL is not
> interrupt-safe.
:SIGIO

From: Raymond Toy on 31 Mar 2010 11:42
On 3/31/10 2:28 AM, Norbert_Paul wrote:
> Raymond Toy wrote:
>> What swank:*communication-style* do you use? I think, but I'm not sure,
>> that anything other than :fd-handler is suspect. CMUCL is not
>> interrupt-safe.
> :SIGIO
>

IIRC, this will cause signals to be generated when IO is needed. That's
causes problems with cmucl. I'd recommend using :fd-handler. :spawn
might work, but I've used :fd-handler ever since I started using slime
many years ago.

Ray

From: Norbert_Paul on 1 Apr 2010 05:11
Raymond Toy wrote:
> IIRC, this will cause signals to be generated when IO is needed. That's
> causes problems with cmucl. I'd recommend using :fd-handler. :spawn
> might work, but I've used :fd-handler ever since I started using slime
> many years ago.
OK. How do I use it?
From: Raymond Toy on 1 Apr 2010 08:45
On 4/1/10 5:11 AM, Norbert_Paul wrote:
> Raymond Toy wrote:
>> IIRC, this will cause signals to be generated when IO is needed. That's
>> causes problems with cmucl. I'd recommend using :fd-handler. :spawn
>> might work, but I've used :fd-handler ever since I started using slime
>> many years ago.
> OK. How do I use it?

In ~/.swank.lisp, just add:

(setf swank:*communication-style* :fd-handler)

Ray

 | 
Pages: 1
Prev: Does slime introduce errors into cmucl?
Next: Currying and Cleave in Common Lisp