in reply to Passing command-line arguments to a file

This is a system question. You need to put all dangerous sequences in double quotes. The shell doesn't know which belongs where.
-s -t -H -a sample.txt ">" sample.html
This will let you set it into @ARGV, however, depending upon what you are trying to do, this may not be the desired result. Unless you are exec'ing with the @ARGV as arguments, the output wont be put into sample.html.

Replies are listed 'Best First'.
Re: Re: Passing command-line arguments to a file
by nysus (Parson) on Apr 17, 2001 at 11:13 UTC
    That's the problem. SEC isn't looking for the output file in @ARGV. It relies on the shell to do the work. Sorry I wasn't more clear on this but I'm tired as hell.