On 1:28 AM 2/26/01 [EMAIL PROTECTED] wrote:

> with specific reference to BBedit I don't think it's good that it
> doesn't check if MacPerl is running before trying to pass it a
> script.

I'm not sure I understand.  This was done for the convenience of our
users.  If MacPerl isn't running why should the user have to go and find
it and launch it first before sending a script to it to execute?  That
is what computers are for.  BBEdit knows where MacPerl is, and launches
it for you.

> Have you tried switching to the MacPerl app through the applications
> menu and force quiting it, then switching back to BBedit and killing
> the apple event.

In BBEdit 6 there is a progress dialog that appears whenever a perl
script takes longer than 2 seconds.  MacPerl gives me no reliable way to
cancel a script in progress.  So the dialog goes up, and allows you to
switch to MacPerl and press command-. there which will terminate the
script.

-- 
Jim Correia                                Bare Bones Software, Inc.
[EMAIL PROTECTED]                     <http://web.barebones.com>

Reply via email to