New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
quote bug in shell command on windows #6416
Comments
From holli.holzer@gmail.comgood localtime() I was told to write here after a conversation on irc. when i run the shell qq[echo "foo"]; the output is \"foo" which is incorrect. It should be "foo" This bug effectively prevents from shelling out to a program while using tx for listening |
From @stmukOn Windows 10 rakudo star 2017.07 I get \"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 <perl6-bugs-followup@perl.org> wrote:
-- |
The RT System itself - Status changed from 'new' to 'open' |
From @stmukI don't think this is a bug in the shell command on windows since cmd.exe behaves differently to Bourne type shells. UNIX Windows |
From @stmukThere 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. |
From @zoffixznetOn Fri, 06 Oct 2017 09:49:54 -0700, steve.mynott+bitcard@gmail.com wrote:
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]/;" While the presence of quotes is a thing of Windows's shell, looks like rakudo tries to escape the quotes (incorrectly?) and the slashes make it into the output |
From @zoffixznetPossibly introed by this commit: MoarVM/MoarVM@05a7dc3 |
Migrated from rt.perl.org#131814 (status was 'open')
Searchable as RT131814$
The text was updated successfully, but these errors were encountered: