> I could write an additional BBEdit extension (or add a preference option > to the current extension) that when run will switch to MacPerl, and send > the contents of the active BBEdit window to MacPerl to be executed as > though it were run using the Run Script command (e.g., STDOUT is sent to > the MacPerl STDOUT window). This would solve problems (a) and (b). Would > anyone use this? Brad, I'd like two scripts that do this: A. Check MacPerl Syntax Save front BBEdit window if (!exists) open a small BBEdit window called "MacPerl STDOUT" Switch to MacPerl Check Syntax on file and show results in the BBEdit STDOUT window. B. Run Perl Script Save front BBEdit window if(!exists) open a small BBEdit window called "MacPerl STDOUT" Switch to MacPerl Run file with STDOUT >> BBEdit STDOUT window. Refresh contents of any BBEdit windows displaying files that were changed by the Perl script. And, I'd like a couple of buttons on a tool bar (like HTML tools) that I can click to execute these two scripts. Since you kinda volunteered to maybe do something, I thought I'd let you know _exactly_ what I'd most like to have. My preference for showing STDOUT in a BBEdit window is that I want to be able to see stdout and my program at the same time. BBEdit hides when I switch to MacPerl. If there's a way to let me see both the MacPerl STDOUT window and the BBEdit script window at once, then its OK to use the MacPerl window instead. The feature of updating open BBEdit file windows would be a real help. Currentlly I have to close the BBEdit window and the Open Recent to refresh the display. --John Springer _______________________________________________________________________ | Can you use a creative, Internet-savvy marketing guy? | | Check Me Out at <http://www.scruznet.com/~springer/HireMe> | | | | [This Space Paid For by the California Employment Development Dept] | |_____________________________________________________________________|