#116 stop interactions w/o resetting messages

[Christopher Haynes]

If tracing or error output messages are appearing in the
interactions window fast enough that you can't easily
read or otherwise capture them you've got a real
problem, because the only way to stop the output may
be to reset the interactions window, which eliminates
the messages.

[Charles Reis]

Logged In: YES
user_id=429731

That's a good idea. I'm going to reclassify this as a
feature request, but I think there should be some state
between killing the JVM and clearing the Interactions window
(at least optionally).

This might also be accomplished by adding a "Suspend" to the
debugger, which we didn't have time for over the summer, but
which would be nice.

[Eric E. Allen]

Logged In: YES
user_id=429660

If we could save arbitrary interactions state, we could solve this problem by adding a break button in addition to the reset button. Before each execution in interactions, we could serialize the interactions state, and restore if the new computation is aborted. BTW, the DrScheme guys are always bringing up the fact that we don't have a break button.

BTW, I _think_ we should be able to do this simply by serializing the DynamicJava interpreter instance...

-- Eric