Bart Lateur <[EMAIL PROTECTED]> wrote:
>If, however, the built-in editor got just that little bit better, people
>might find that they hardly ever need an external editor, at all.
My sentiments exactly - the external editors exist because they fill the
gap left by the MacPerl app's own editing functions (or lack of). I have
tried all of the editors which are frequently named on this list, and all
have their pros and cons, but the single biggest con that doesn't change
whatever editor you use, is the amount of juggling to do in one way or
another simply because the Perl interpreter is not part of the editor.
But in the same way countries get the governments they deserve, so user
groups get the software they deserve. This discussion came up already back
in the summer of 99 when Brian McNett was trying to port the WASTE api to a
Macperl usable lib and nobody was really that concerned about it, at least
nobody that had the technical ability required for such a project (I'm in
no way knocking Brian McNett's efforts, I only wish I had now and had had
then the knowledge to help him with the porting). I guess everyone's just
sitting around waiting for OS X to solve everything
- [MacPerl] Re: Textengine for Macperl. [was: The State of... Alan Fry
- [MacPerl] Re: Textengine for Macperl. [was: The Sta... David Steffen
- Re: [MacPerl] Re: Textengine for Macperl. [was: The... Bart Lateur
- [MacPerl] Re: Textengine for Macperl. [was: The Sta... Alan Fry
- Re: [MacPerl] Re: Textengine for Macperl John Delacour
- Re: [MacPerl] Re: Textengine for Macperl. [was: The... Jan Erik Moström