It may help to write a little test program, like this:
>> write %trim.r {
{ [
{ rebol []
{ write %text.txt mold system/script/args
{ ]
{ }
and view the contents of %test.txt. Given the example of:
rebol -swq trim.r file1.in file2.out
I get:
"file1.in file2.out"
in %test.txt. Try it out for your self and see. Then your problem should
be obvious. If not, let's know about it.
Andrew Martin
ICQ: 26227169
http://members.xoom.com/AndrewMartin/
-><-
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, 10 March 2000 6:26 PM
Subject: [REBOL] Command Line Args Re:
>
> I tested it on my machine (running Win95) and it worked as advertised,
i.e.
> the arguments were available under system/script/args as a string.
>
> What did you expect would happen? Perhaps the problem is with trim.r?
>
> At 09:04 PM 3/9/00 -0500, you wrote:
> >Can some one please send me a example of how to deal with
> >command lind arguments please?
> >
> >I want to do some thing like this from the command line:
> >
> >rebol -swq trim.r file.in file.out
> >
> >Manual says I should see "file.in and file.out" at
> >system/script/args but I don't.
> >
> >What am I doing wrong?
> >
> >
> >
>
> ;- Elan >> [: - )]
>
>
