[TxMt] for perl development

[Noah M.Daniels]

On Dec 20, 2004, at 8:55 AM, Allan Odgaard wrote:

> On Dec 19, 2004, at 18:32, Noah M.Daniels wrote:
>
>> [...] there are a couple of things still missing, IMHO.
>
> I'm only aware of a single item [1] that kept 1.0.2 from being my 
> final release -- I apologize for this obvious negligence, but as a tea 
> drinker I am heavily biased toward letting it make tea before it can 
> make coffee ;)
>

So a full-fledged Turkish coffee isn't likely until 2.0?

>> First, the Perl syntax bundle doesn't handle POD [...] it would be 
>> ideal if it could do as good a job as BBEdit's syntax coloring for 
>> Perl/POD.
>
> Well... I never used BBEdit and I don't program in Perl -- but if 
> there is anything limiting users in supporting various language 
> constructs, I'd like to know about it (and I'm already aware of lack 
> of recursion and back references in the end pattern (for heredocs) 
> which I hope to have fixed for 1.1.1, along with some other 
> improvements).
>

POD is pretty easy - a line beginning with '=' (i.e. =begin, =head1, 
=synopsis) begins a POD block; a line beginning with '=cut' ends the 
POD block. It's basically Perl's built in documentation system that 
also doubles as a method of block-commenting. All you really have to do 
is treat it as block comments, with any line starting '=' beginning a 
comment block, and any line starting '=cut' ending one. Yes, the '=' 
must be the first character on the line. When people use it for 
documentation, you'll see extra '=' directives in the middle (i.e. 
'=item1' and such) but that should be irrelevant. In other words, 
blocks do not nest; =cut closes ALL POD and returns you to code.


>
> As of such, there's nothing built-in, but there's a few default bundle 
> items.  TextMate is a general purpose text editor, and for most of 
> what you want as build-in, I'm certain the majority doesn't need it.
>

Yeah, the more I play with the ability to add custom commands, the more 
I realize my request was unnecessary. What *would* be nice would be 
better control over the window that pops up if one chooses a new window 
to display the output of the command - perhaps the ability to specify 
the window size/position.
>

--
"Failure is not an option, it comes bundled with the software" -DefCon 
10
Noah M. Daniels
ndaniels at mac.com