re: [MacPerl] MacPerl's Editor

[robinmcf]

<DISCLAIMER> whatever information is given in this email is not intended to start a Holy War </DISCLAIMER> >>[EMAIL PROTECTED] (Jim Correia) wrote: >>Define what you mean by interactively please. 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. Being wary of getting into a pantomime chorus about the various merits of the editors people use, I 'll move off onto a hypothetical tangent: lets say Company A makes product A, and Joe B maintains shareware app B. In both cases if I don't like function C or layout D, I write to whoever and say so. Then I get back a reply along the lines of 'unless everybody wants that you'll just have to lump it'. Now most people who use MacPerl can program perl, so what I'm suggesting is to make an editor shell which gives basic editing facilties, but with lots of hooks thereby enabling the development of editor modules in Perl for the editor. >On 3:38 PM 2/25/01 "Ken Williams" <[EMAIL PROTECTED]> wrote: > Mostly I just mean using STDIN and STDOUT to ask questions and give >answers in the console > window. I haven't used Mac-specific stuff very much (dialogs, file >finding dialogs, etc.) so I > can't speak to how smoothly that works when editing externally. 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.