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.
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"
On Fri, 06 Oct 2017 09:49:54 -0700, steve.mynott+bitc...@gmail.com wrote:
> I propose this ticket be closed.
No, there's definitely some bug exists. On 2017.07 Star, I get this (\x[22] is
the double-quote char):
C:\Users\zoffix>perl6 -e "say qqx/echo \x[22]foo\x[22]/;"
\"foo\"
While the
On Fri, 06 Oct 2017 09:49:54 -0700, steve.mynott+bitc...@gmail.com wrote:
> I propose this ticket be closed.
No, there's definitely some bug exists. On 2017.07 Star, I get this (\x[22] is
the double-quote char):
C:\Users\zoffix>perl6 -e "say qqx/echo \x[22]foo\x[22]/;"
\"foo\"
While the
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 wrote:
> # New T
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 wrote:
> # New T
# New Ticket Created by Holli Holzer
# Please include the string: [perl #131814]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131814 >
good localtime()
I was told to write here after a conversation on irc. when i run the
fo
