In einer eMail vom 15.03.00 06:44:43 (MEZ) Mitteleuropäische Zeit schreibt
[EMAIL PROTECTED]:
> The trick seems to be calling 'change-dir system/script/parent/path' near
the
> start of the script to get 'normal' current directory behavior.
> If there are associated scripts that live in the same
I had a some difficulty myself with trying to get the current directory and
was convinced there was a bug in REBOL.
system/script/parent/path is the directory where rebol (or an auto-running
script) was invoked from the command line.
system/script/path is the directory what-dir returns and what
ite %test2/where-core.bat form [{"C:\rebol031\rebol"} "..\test\where.r"]
write %test3/where-path.bat form ["path ..\test2;%path%^/" "where-core"]
exit
In einer eMail vom 14.03.00 12:22:09 (MEZ) Mitteleuropäische Zeit schreibt
[EMAIL PROTECTED]:
<<
>If you want to use the directory of the bat file that launched the script
>then technically it is the parent of the script.
>
>You will find that path of that in system/script/parent/path
True, but if trim.bat and trim.r are both in the same
directory in the path, say N:\UTL, and I run from the
If you want to use the directory of the bat file that launched the script
then technically it is
the parent of the script.
You will find that path of that in
system/script/parent/path
so If I used the following line in bat file located in at c:/temp
rebol.exe %/d/demo/test.r args.txt
; The res
Hi,
I've run into the same problem, and it really makes my applications more
difficult to develop for end user simplicity.
I like your suggested solution. Have you submitted it to [EMAIL PROTECTED]?
Regards,
Bernie Schneider
Systems Analyst
CIBER, Inc.
303-224-4159
[EMAIL PROTECTED]
> -O
