Skip Menu |

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

Report information
The Basics
Id: 73580
Status: resolved
Priority: 0/
Queue: Pod-Perldoc

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

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



Subject: perldoc does not recognize itself in $0
'perldoc' without arguments shows a message indicating that it didn't recognize itself in $0: ------8<------8<------8<------8<------8<------8<------8<------8<------8< You called the perldoc command with a name that I didn't recognize. This might mean that someone is tricking you into running a program you don't intend to use, but it also might mean that you created your own link to perldoc. I'll allow this if the filename looks only has [a-zA-Z0-9._-]. at /home/dolmen/.perl/bin/perldoc line 9 Usage: perldoc [-hVriDtumFXlT] [-n nroffer_program] [-d output_filename] [-o output_format] [-M FormatterModule] [-w formatter_option:option_value] [-L translation_code] PageName|ModuleName|ProgramName Examples: perldoc -f PerlFunc perldoc -q FAQKeywords perldoc -v PerlVar The -h option prints more help. Also try "perldoc perldoc" to get acquainted with the system. [Perldoc v3.15_14] at /home/dolmen/.perl/bin/perldoc line 9 ------8<------8<------8<------8<------8<------8<------8<------8<------8< This is Pod::Perldoc 3.15_14 installed on perl 5.10.1 on Ubuntu in /home/dolmen/.perl. -- Olivier Mengué - http://perlresume.org/DOLMEN
Can you try the latest in Github? It doesn't change anything, but I add the values of $0 in the output so we can see why it's not matching the pattern. https://github.com/briandfoy/Pod-Perldoc Thanks,
Show quoted text
> This is Pod::Perldoc 3.15_14 installed on perl 5.10.1 on Ubuntu in > /home/dolmen/.perl.
I uploaded 3.15_15 to CPAN - would you please retry and report the value of $0 from the error output? Thanks. P.S. Thanks for pointing out the spurious semi-colons in the Makefile.PL
This was due to a missing '?' in a regex. Fixed in 3.16. Thanks for bug report!