Skip Menu |

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

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

People
Owner: Nobody in particular
Requestors: renato.cron [...] gmail.com
Cc:
AdminCc:

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



Subject: bad encoding after formatting via vscode
Date: Sun, 16 Aug 2020 22:54:21 -0300
To: bug-perl-tidy [...] rt.cpan.org
From: Renato Santos <renato.cron [...] gmail.com>
Hello, I'm using the latest version of vscode (1.48.0) and when I try to format this code: use strict; use utf8; is 'foo', 'bar';# aaa is 'foção','bar'# aaa with Perl::Tidy@20200110 I get: use strict; use utf8; is 'foo', 'bar'; # aaa is 'foção', 'bar' # aaa which have the spacing wrong on the comment because of encoding, but that's fine, because when I upgrade to Perl-Tidy-20200619 and try to format, I get this: use strict; use utf8; is 'foo', 'bar'; # aaa is 'fo��o', 'bar' # aaa The spacing of comments are right (cool!), but the char is different When I run with the command line, it's working, so I guess is something to do with vscode I'm using the 'perl' extension, and have this on my settings: "[perl]": { "editor.defaultFormatter": "cfgweb.vscode-perl" }, "perl.perltidy": "/usr/bin/perltidy", "perl.perltidyArgs": [ "-pbp", "-w", "-l=120", "-mbl=2", "-i=4", "-ci=2", "-vt=0", "-pt=2", "-bt=2", "-sbt=2", "-isbc", "-nst", "-boc" ], when I add "--character-encoding=none" it fixes the output (but the comment spacing is back to the first example) I tried adding "--character-encoding=utf8", "--use-unicode-gcstring", "-utf8" but I get the same result (bad encoding) I'm on without a limited internet right now, so I can't install other versions of vscode to test vscode perl extension is named 'perl' from 'cfgweb' version 1.18.0. I tried disabling it and installing "simple perl" of Zhiyuan Lin and I got the same issue (they both uses the binary found on path or configured on settings) Thank you all

Message body is not shown because it is too large.

Hi, Sorry for the delayed response, I've been away. This looks like it may be the same issue as reported in RT #133166. I expect to put out a release which fixes it in a few days. Thanks, Steve
version 20200822 has been released with a fix for this problem. Thanks for reporting this bug.