Thanks Vicki... Is all this documented somewhere? I must have missed it. I tried it and it works great! Will In a message dated 6/15/99 12:16:58 PM, you wrote: >At 10:55 -0400 6/3/99, WAMerrill@aol.com wrote: >>> When you run a MacPerl script directly from BBEdit 5.1 using the new >>> PERL Palette Run option, if the script happens to print to STDOUT, the >>> output will go to another BBEdit Window called "MacPerl Output". I >>> never saved this output in the past, but this time accidently saved it >>> just after closing the window without realizing it. (it asks you if you >>> want to save the changes to MacPerl Output - I've always done a shortcut >>> for Don't Save: cmd-D). If you do happen to save the output, it places >>> it in the BBEdit Application Folder (BBEdit 5.0:MacPerl Support:MacPerl >>> Output). If you run the same script again, it appends to the same file >>> you just saved - your output will thus contain the old output plus your >>> new output. > >If you option-click on the Run button in the palette, you get a preference >dialog for this sort of thing, with various check boxes to modify the >behaviour, as: > > [] Selection Only [] Use Perl Debugger > [] Save before Running [] Bring MacPerl to Front > [] chdir to Script's Folder > > > Output to: Output Options: > > O New Window [] Clear before writing > O MacPerl Output File [] Save After Writing > O filename.log > > >If you check "Clear Before Writing" you won't keep appending STDOUT to the >same place over and over. ===== Want to unsubscribe from this list? ===== Send mail with body "unsubscribe" to macperl-request@macperl.org