Skip Menu |
 

This queue is for tickets about the Devel-PerlySense CPAN distribution.

Report information
The Basics
Id: 42827
Status: resolved
Priority: 0/
Queue: Devel-PerlySense

People
Owner: Nobody in particular
Requestors: Jan.Tatarik [...] mBalance.com
Cc:
AdminCc:

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



Subject: Flymake warnings not displayed with latest Perl::Critic
Date: Tue, 27 Jan 2009 13:44:03 +0100
To: JOHANL via RT <bug-Devel-PerlySense [...] rt.cpan.org>
From: Jan Tatarik <Jan.Tatarik [...] mbalance.com>
Download (untitled) / with headers
text/plain 575b
After upgrading to Perl-Critic-1.094001 and Devel-PerlySense-0.0177 at the same time, emacs will not display perlcritic warnings any more. 'perly_sense flymake_file' now produces messages whose format is not recognized by flymake. This is due (I guess) a new way the warning format is specified in Perl::Critic::Violation. Changing line 561 of Project.pm from local $Perl::Critic::Violation::FORMAT = "%m near '%r' (%e, %p) at %f line %l.\n"; to Perl::Critic::Violation::set_format("%m near '%r' (%e, %p) at %f line %l.\n"); fixes the problem for me. Thanks, Jan
RT-Send-CC: Jan.Tatarik [...] mbalance.com
Download (untitled) / with headers
text/plain 104b
Fixed in 0.0189, on it's way to CPAN now. Thanks for the bug report, and sorry for the tardy fix. /J


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.