On Mon, Dec 23, 2013 at 04:05:15PM +0100, Ingo Schwarze wrote:
> Andrew Fresh wrote on Sun, Dec 22, 2013 at 06:24:17PM -0700:
> > On Mon, Dec 23, 2013 at 01:32:54AM +0100, J'er'emie Courr`eges-Anglas wrote:
>
> >> I thought that this module only fetched data and fed it into our base
> >> pod forma
Hi,
Andrew Fresh wrote on Sun, Dec 22, 2013 at 06:24:17PM -0700:
> On Mon, Dec 23, 2013 at 01:32:54AM +0100, J'er'emie Courr`eges-Anglas wrote:
>> I thought that this module only fetched data and fed it into our base
>> pod formatter, but if it does more that may be a better choice indeed.
> As
On Mon, Dec 23, 2013 at 01:32:54AM +0100, J'er'emie Courr`eges-Anglas wrote:
> I thought that this module only fetched data and fed it into our base
> pod formatter, but if it does more that may be a better choice indeed.
As far as I know the above is correct. It overloads the standard
Pod::Perld
Ingo Schwarze writes:
> Hi,
>
> Jérémie Courrèges-Anglas wrote on Mon, Dec 23, 2013 at 12:48:08AM +0100:
>> Andrew Fresh writes:
>
>>> I wasn't actually sure where it should live, so please critic.
>
>> At first I'd have put it in misc. devel and sysutils kinda make
>> sense too, but "devel is
Hi,
Jérémie Courrèges-Anglas wrote on Mon, Dec 23, 2013 at 12:48:08AM +0100:
> Andrew Fresh writes:
>> I wasn't actually sure where it should live, so please critic.
> At first I'd have put it in misc. devel and sysutils kinda make
> sense too, but "devel is too crowded" and putting it under s
Andrew Fresh writes:
> I'm sure there must be something wrong as making this port this was too
> simple. But anyway , "alias perldoc=cpandoc" makes my life better.
Looks fine.
> I wasn't actually sure where it should live, so please critic.
At first I'd have put it in misc. devel and sysutil
