Tue Jan 18 15:43:37 2011user42 [...] zip.com.au - Ticket created
Subject:
PodView and =for
Date:
Wed, 19 Jan 2011 07:41:42 +1100
To:
bug-Prima [...] rt.cpan.org
From:
Kevin Ryde <user42 [...] zip.com.au>
I had some pod with
=for stopwords foo bar quux
and Prima::PodView showed the "foo bar quux" as ordinary text.
I think normally =for should be ignored if it's not a hint etc
the viewer in question understands.
Thu Jan 20 12:58:01 2011KARASIK [...] cpan.org - Correspondence added
Can't reproduce. Can you give a minimal pod file that shows the problem?
Thu Jan 20 12:58:01 2011The RT System itself - Status changed from 'new' to 'open'
Thu Jan 20 16:48:16 2011user42 [...] zip.com.au - Correspondence added
Subject:
Re: [rt.cpan.org #64898] PodView and =for
Date:
Fri, 21 Jan 2011 08:48:18 +1100
To:
bug-Prima [...] rt.cpan.org
From:
Kevin Ryde <user42 [...] zip.com.au>
"KARASIK via RT" <bug-Prima@rt.cpan.org> writes:
Show quoted text
>
> Can you give a minimal pod file that shows the problem?
Oh, I see it's when the =for is more than one line, per below.
(perlpodspec allowing multi-line command paragraphs ... I suppose
Pod::Parser or Pod::Simple could take care of that sort of syntax
nonsense. I'd rate Pod::Parser as easier, but Pod::Simple is much
better at breaking down L<> links.)
=for stopwords this is a stopwords paragraph
of more than one line
=head1 NAME
foo -- a program called foo
=cut
--
On Tuesday the Australian Literature department at the University of
Sydney announced an important advance in the field: they found some.
Fri Jan 21 05:08:30 2011KARASIK [...] cpan.org - Correspondence added
fixed
Fri Jan 21 05:08:30 2011KARASIK [...] cpan.org - Status changed from 'open' to 'resolved'
RT for rt.cpan.org