Re: [perl #128154] [BUG] Cannot use qqx in rakudo star on windows7

I'm not sure. Probably your idea of warning about detected encoding is better. S On Thu, 12 Jul 2018 at 09:58, Kamil Kułaga via RT wrote: > > Will it work fine for utf-16 users? > On Wed, Jul 11, 2018 at 11:16 AM Steve Mynott via RT > wrote: > > > > Maybe the Windows p

Re: [perl #128154] [BUG] Cannot use qqx in rakudo star on windows7

Maybe the Windows port of rakudo should set this automatically on startup? On Wed, 11 Jul 2018 at 10:08, Kamil Kułaga via RT wrote: > > I found resolution. It looks like it is problem windows locale issue than > perl itself. > > Running command > > chcp utf8 > > Makes work just fine. Default

Re: [perl #128520] [META][RT][RFC] Consider migrating from RT

Maybe the ticket should be closed if/when the RT bug tracker is closed to new tickets itself and references to RT removed from all docs? S On 5 March 2018 at 17:50, Zoffix Znet via RT wrote: > On Wed, 11 Oct 2017 13:22:50 -0700, alex.jakime...@gmail.com wrote: >>

[perl #131814] quote bug in shell command on windows

There does seem to be a quoting bug in Windows shell but none of the above examples show it. See #132183: Insufficient debug messages from zef/perl6.bat when package build fails I propose this ticket be closed.

[perl #131814] quote bug in shell command on windows

I don't think this is a bug in the shell command on windows since cmd.exe behaves differently to Bourne type shells. UNIX $ echo "foo" foo Windows C:\Windows\system32>echo "foo" "foo"

Re: [perl #132183] Insufficient debug messages from zef/perl6.bat when package build fails

signal => 0, command => ["perl -e \"use v5.18;\""]) >> > > Problem isn't lack of Perl 5: > > PS C:\rakudo> perl -v > > This is perl 5, version 26, subversion 0 (v5.26.0) built for > MSWin32-x64-multi-thread > > > Regards, > Ville > >

Re: [perl #132183] Insufficient debug messages from zef/perl6.bat when package build fails

It seems a bit unfair ("shooting the messenger") blaming zef for module install error messages and after all it does says "Perl 5 version requirement not met" Looking at what triggers this error... https://github.com/niner/Inline-Perl5/blob/master/Build.pm#L6 suggests you need 5.18 or better

Re: [perl #130500] [LTA] Download Page on Rakudo.org

That looks better thanks! One suggestion might be to remove the 32 bit windows MSI link (part of a 2x2 matrix of links) since its not being actively maintained and the last one dates from 2016.01. Of course part of the problem with doing this is that it doesn't really fit in with 2x2 so maybe

Re: [perl #131814] quote bug in shell command on windows

On Windows 10 rakudo star 2017.07 I get \"foo\" Proc.new(in => IO::Pipe, out => IO::Pipe, err => IO::Pipe, exitcode => 0, signal => 0, command => ["echo \"foo\""]) whereas on FreeBSD 10 I get foo only (no quotes or Proc.new structure) S On 29 July 2017 at 16:29, Holli Holzer

Re: [perl #131815] `zef search` fails after installing `rakudo-star-2017.07-x86_64 (JIT).msi` on Windows 10 Home x64

I can't reproduce on Windows 10 Professional. Was there a previous Rakudo Star install present? You could try cd %USERPROFILE% rd /s .zef rs /s .perl6 and rerunning. S On 29 July 2017 at 18:08, Richard Loveland wrote: > # New Ticket Created by Richard

Re: [perl #127308] Configure.pl with moar fails to find C compiler on older Darwin

My guess is that the PPC version of OS X probably still has the real GCC as its compiler rather than clang as on more modern systems. You could try looking for the config line which contains the definiton of clang for OS X/darwin and changing it to gcc or if you are using rakudobrew maybe

[perl #126927] [BUG] Spurious warning when trying to smartmatch num64 against Num in Rakudo

Bisected to f457007181bb6e2dcb6aefe857f36d648ae38401

Re: [perl #123758] panda doesn't cope well when projects.json isn't a JSON document

This error message (seen with Virgin UK) was fixed yesterday so I assume if Paul was seeing this today he was using an old version -- maybe the one in Star. The behaviour I saw was a zero length projects.json. On 8 February 2015 at 14:04, Moritz Lenz via RT perl6-bugs-follo...@perl.org wrote: