Hi, Daniel,

It should be fine to quit without saving.  All of the code you 
entered is already safely preserved in the .changes file.

Cheers,

  -- Scott


At 3:39 PM -0500 3/29/05, Daniel Salama wrote:
>Scott,
>
>Thanks for the prompt reply. Should I do this while the hung VM 
>continues running or should I quit it without saving?
>
>Thanks,
>Daniel
>
>On Mar 29, 2005, at 3:36 PM, Scott Wallace wrote:
>
>>Hi, Daniel,
>>
>>Open up a *healthy* image, and from within a file-list in that 
>>healthy image navigate to the .changes file of the *sick* image, 
>>and hit the "recent changes" button.  This will give you a 
>>change-list browser on your lost code.
>>
>>Cheers,
>>
>>  -- Scott
>>
>>At 3:28 PM -0500 3/29/05, Daniel Salama wrote:
>>>Hi guys (it's me again :) )
>>>
>>>Question: I ran a process in Squeak and by mistake I wrote in my 
>>>code to inspect a variable inside of a loop. Now, when the process 
>>>is run, the code tries to open 127,000+ inspect windows and so far 
>>>the VM seems unresponsive (wouldn't be surprised). Is there a way 
>>>to force the code to stop running? What I'm really interested in 
>>>is saving the code that I wrote (I ran the process before saving 
>>>the image). Is there a way to save a copy of a running image while 
>>>the VM is unresponsive? I'd hate to have to retype all my code.
>>>
>>>Thanks,
>>>Daniel