Skip Menu |

This queue is for tickets about the Perl-Tidy CPAN distribution.

Report information
The Basics
Id: 75377
Status: resolved
Priority: 0/
Queue: Perl-Tidy

People
Owner: Nobody in particular
Requestors: pdagosto [...] edgebio.com
Cc:
AdminCc:

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



The option -sbcp (--static-block-comment-prefix) seems to be ignored if specified in the .perltidyrc file. My .perltidyrc file contains: --logfile --static-block-comments --static-block-comment-prefix="^#{2,}[^\s#]" Which means that the following code: sub foo { my ( $arg1, $arg2 ) = @_; #################### # # arguments: $arg1, $arg2 # # return value: undef # #################### print "\$arg1 = $arg1\n"; print "\$arg2 = $arg2\n"; return; } should be reformatted to look like: sub foo { my ( $arg1, $arg2 ) = @_; #################### # # arguments: $arg1, $arg2 # # return value: undef # #################### print "\$arg1 = $arg1\n"; print "\$arg2 = $arg2\n"; return; } as per the documentation on CPAN. And this works when those options are specified from the command line along with -npro to ignore the .perltidyrc file. However, when the .perltidyrc file is used and the only command line option specified is --DEBUG the log file shows that --static-block-comment-prefix is ignored: perltidy version 20101217 log file on a linux system, OLD_PERL_VERSION=5.010001 Found Configuration File >>> .perltidyrc Configuration and command line parameters for this run: --logfile --static-block-comments -DEBUG Note: I've also tried using single quotes around the value for the option but that doesn't work either. My Perl version is 5.10.1 and I'm on CentOS 6
fixed in perltidy 20120619