[Ecls-list] [PATCH RESEND] Fix the value of the print-function depth parameter in defstruct.

[Alexander Gavrilov]

On Wed, Oct 7, 2009 at 1:30 PM, Juan Jose Garcia-Ripoll
<juanjose.garciaripoll at googlemail.com> wrote:
> Let me now add a kind of transcript of a typical session with Ctrl-C
> and ask you to reproduce it. Note that processes do not get
> interrupted immediately, they only get suspended. If you want to
> interrupt a given thread, you have to use a restart (:r2) Could you
> (and anybody else reading this) try it?

This seems to work now, but:

1. What about :continue after having interrupted a thread?
2. The second Ctrl-C kills the interpreter in most cases.
3. :br does not work at all:

CL-USER[1]> :br
Command aborted.
Received condition: The function SI::TPL-INTERRUPT-COMMAND is undefined.


Also, if there is only one non-signal thread running, why can't it be
interrupted automatically as a simplified special case?

Alexander