Skip Menu |

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

Report information
The Basics
Id: 81387
Status: resolved
Priority: 0/
Queue: Pod-Parser

People
Owner: Marek.Rouchal [...] gmx.net
Requestors: rdiezmail-temp2 [...] yahoo.de
Cc:
AdminCc:

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



Subject: 2 suggestions for module Pod::Usage
I tried e-mail but the messages bounce back. So I created this "bug" report. Hi there: Here are 2 suggestions for module Pod::Usage : 1) Documentation: Would it be worth adding a reference to the FindBin module next to this paragraph? In the pathological case that a script is called via a relative path and the script itself changes the current working directory (see chdir in the perlfunc manpage) before calling pod2usage, Pod::Usage will fail even on robust platforms. Don't do that. For example, this appears to work: -input => $FindBin::Bin . "/" . $FindBin::Script 2) It would be nice to have the option to use Pod::Text::Termcap for the backend. I have written scripts with embedded POD documentation, and I'm using Pod::Usage to generate the output for command-line switch '--help'. The script can detected whether it's running on a real console (instead of outputting to a redirected file) and use that Termcap module for bold, underlined text and so on. Many thanks, rdiez
Will be in Pod::Usage 1.60.