# from Andy Armstrong
# on Thursday 07 June 2007 03:13 pm:
>I'd like an editor that lets me look at it either way. Sometimes I
>want to look at uninterrupted code - in which case interleaved
>documentation just gets in the way. Other times it's nice to be able
>to read the code while documenting it - in which case interleaved
>would be better.
I've played with this folding scheme, but really wish vim had a way to
anchor it to the front of the line. What it does with head1/head2 can
be pretty useful (folding an entire head1 and all of the code) but
honestly I've had foldenable turned off for quite a while now.
:set foldmethod=marker
:set foldmarker=\=head,\=cut
Maybe there's a better folding module in vim? It would be nice if it
could recognize and fold pod plus the related blank lines.
I've never seen the benefit of pod after __END__. IMO, your code and
docs should follow the same order/groupings. That, and you have to
retype method names and such in POD anyway, so separating them just
risks too much drift. On a related note, I haven't come up with a good
answer for documenting accessors. See usage2pod().
--Eric
--
Consumers want choice, consumers want openness.
--Rob Glaser
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
