The methods to invoke the emergency evaluator are nice, but not what I
was looking for. While experimenting with raw and morphic events I
usually can't tell where things blow up and so I can't predict the
places where I should place fallbacks to the emergency evaluator. And
when the event processing chain is broken because of a MNU error caused
by a typo in a method that I just accepted, I'm stuck and can't do a
thing, because keyboard and mouse events won't be processed anymore. So
the only solution is to quit and reload the image.
I thought there was a key combination that triggers the emergency
evaluator directly from the vm. From within the emergency evaluator I
would be able to do "revert last accepted method" and everything would
be fine. I know I always can find the answer by looking at the source
files, but at the time of writing they wasn't accessible to me. So I
dared to ask here. :)

Alex

-----Ursprüngliche Nachricht-----
Von: squeak-dev-bounces at lists.squeakfoundation.org
[mailto:squeak-dev-bounces at lists.squeakfoundation.org] Im Auftrag von
Bert Freudenberg
Gesendet: Freitag, 20. Juni 2003 15:56
An: The general-purpose Squeak developers list
Cc: Alexander Lazarevic
Betreff: Re: Emergency Evaluator

Am Freitag, 20.06.03 um 08:19 Uhr schrieb Alexander Lazarevic:

> Hi!
>  
> Is there a way to force the emergency evaluator to show up (with the 
> windows/linux vm)?

Type "emergency" somewhere. Press Ctrl-E. You see methods that probably 
deal with the emergency evaluator.

 From this you see that you can do

	self primitiveError: 'foo'

which is the normal failure procedure or

	Transcripter emergencyEvaluator

if you want to use this in your application.

-- Bert