On 2:40 PM 3/11/00 Larry Moore <ljmoore@freespace.net> wrote: > BBEdit 5.1.1 is a fine piece of work. Congratulations and thanks. I > wondered whether the <AppleEvent> in that line, was because the > saving was inhibited in the demo? Newbe question. That happens because in some circumstances I send the script text to be executed rather than in a file (mostly only when the front window is dirty) so MacPerl reports the error as occuring in the AppleEvent. I thought (but it has been awhile since I looked at the code) that I replaced it on report to refer to the front window. I guess not. It is only a visual problem, as the right line should be selected. I'll look at it. > BTW. is there a way of setting BBEdit to detect the -d switch and > automatically push MacPerl to the front for debugging sessions? BBEdit won't parse the #! line. However, if you hold down the option key, Run turns into Run... and you can force MacPerl to come to the front in that dialog. -- Jim Correia Bare Bones Software, Inc. correia@barebones.com <http://web.barebones.com> # ===== Want to unsubscribe from this list? # ===== Send mail with body "unsubscribe" to macperl-request@macperl.org