John McNamara wrote:
At 20:34 01/04/2005 -0700, Jim Cromie wrote:
> I would like pod to respect my editors defaults,
Ultimately, it would be easier to get your editor to respect pod's defaults.
There is a pod-mode for Emacs that you may find useful:
http://search.cpan.org/~schwigon/pod-mode/ <http://search.cpan.org/%7Eschwigon/pod-mode/>
thanks for that.
and therefore could be construed to interpret as pod processor directives/instructions.
> So, is this counter to the spirit of perlpodspec ? > Or is this kind of scoping precisely what =for is for,
According to perlpod, "[=for] will let you have regions of text/code/data that are not generally interpreted as normal Pod text".
whereas =begin =end provide an explicit scope, forex targeting only HTML rendering
(for the following pod block)
=for *could* be seen as something pertinent to all following pod-text, analogous to the way
a file-my-var is visible to all source following its declaration.
this interpretation would allow it to succinctly specify pod processing directives to the
pod source, not just the pod destination.
However, it would appear that you wish to have regions of almost Pod interpreted as Pod. It think that this *is* counter to the spirit of Pod.well - it is verbatim pod. To the extent that its only for me, Id prefer that
it be more readable in the source (ie indented), vs autowrapped in the target rendering.
It would be nice to have both.
In order not to be disappointed it is usually best to remember that the P in Pod (like peas in a pod) stands for plain. :-)
Sometimes that is constraining, sometimes Pod isn't plain enough.
John. --
thanks John, jimc
