Skip Menu |

This queue is for tickets about the Pod-Markdown CPAN distribution.

Report information
The Basics
Id: 76726
Status: resolved
Priority: 0/
Queue: Pod-Markdown

People
Owner: Nobody in particular
Requestors: DOHERTY [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: (no value)
Fixed in: 1.320



Subject: Command line interface doesn't match the other pod2* utilities
pod2markdown requires input on stdin, and provides output on stdout -- but all the other pod2* utilities take a filename as an argument. pod2markdown should do the same. If you want to provide input on stdin, a file of - is the standard way.
Seems reasonable. Sadly it looks like various modules don't really do it the same way, though searching for others wasn't exactly "easy" (most of the scripts themselves aren't indexed). Were there any pod2* scripts in particular you were looking at? Regardless, Is this the usage you'd expect? pod2markdown in.pod pod2markdown in.pod out.mkdn pod2markdown - out.mkdn pod2markdown On Fri Apr 20 08:00:39 2012, DOHERTY wrote: Show quoted text
> pod2markdown requires input on stdin, and provides output on stdout -- > but all the other pod2* utilities take a filename as an argument. > pod2markdown should do the same. If you want to provide input on stdin, a > file of - is the standard way.
On Wed Apr 25 00:41:53 2012, RWSTAUNER wrote: Show quoted text
> Seems reasonable. > Sadly it looks like various modules don't really do it the same way, > though searching for others wasn't exactly "easy" > (most of the scripts themselves aren't indexed). > > Were there any pod2* scripts in particular you were looking at? > > Regardless, > Is this the usage you'd expect? > > pod2markdown in.pod > pod2markdown in.pod out.mkdn > pod2markdown - out.mkdn > pod2markdown >
You're right, the others are much less consistent than I thought. *barf* Yes, your suggested usage makes a lot of sense.
I released this change earlier today.