in reply to system, pipes, shell, quoting

Could you give an example of a filename or better a complete command string, where quotemeta fails?

I'm not sure I have anything to contribute, but it would be interesting to see where it is failing for you.

Okay you lot, get your wings on the left, halos on the right. It's one size fits all, and "No!", you can't have a different color.
Pick up your cloud down the end and "Yes" if you get allocated a grey one they are a bit damp under foot, but someone has to get them.
Get used to the wings fast cos its an 8 hour day...unless the Govenor calls for a cyclone or hurricane, in which case 16 hour shifts are mandatory.
Just be grateful that you arrived just as the tornado season finished. Them buggers are real work.

Replies are listed 'Best First'.
Re: Re: system, pipes, shell, quoting
by superpete (Beadle) on Nov 13, 2002 at 20:04 UTC 
    #!/usr/bin/perl

$fname = "foo\nbar";

#-- standard idiot-proof open
   $fname = "./$fname" if $fname =~ /^\s/;
   open F, "> $fname\0";

print F "testing 1 2 3\n";
close F;

system("cat \Q$fname\E");      # produces error

unlink $fname;

    [download]
[reply]
[d/l]

      And do you have any way of accessing a file who's name contains an embedded newline from your shell?

      Ie. Can you type the cat command at the CLI and have it work?

      Okay you lot, get your wings on the left, halos on the right. It's one size fits all, and "No!", you can't have a different color.
      Pick up your cloud down the end and "Yes" if you get allocated a grey one they are a bit damp under foot, but someone has to get them.
      Get used to the wings fast cos its an 8 hour day...unless the Govenor calls for a cyclone or hurricane, in which case 16 hour shifts are mandatory.
      Just be grateful that you arrived just as the tornado season finished. Them buggers are real work.

[reply]

In Section Seekers of Perl Wisdom