In the windows 2k environment, I am seeing some interesting quirks from the command line. For these examples, I'm leaving pathnames off, though the effect is the same either way. If I enter the following:
rebol --secure allow -w -q -s script.r c:\filename.txt I can see the filename in system/script/args with no problem. However, if I place a do %script.r in my user.r file, and call it with: rebol --secure allow -w -q c:\filename.txt I get 'none' in my system/script/args var. Also, if I use the -- delimiter which should indicate anything else is passed to rebol as an argument as in: rebol --secure allow -w -q -s script.r -- c:\filename.txt rebol --secure allow -w -q -- c:\filename.txt I get 'none' as well. Any thoughts as to why the variations? One final question. Is there any way to set an environmental var (i.e. ERRORLEVEL) upon exiting? Thanks --- G. Edw. Learned - [EMAIL PROTECTED] (Never apply a Star Trek Solution to a Babylon Five Problem) -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
