Article View: comp.sys.amiga.tech
Article #12894ARexx current directory woes
From: Bryan Ford
Date: Thu, 25 May 1989 09:23
Date: Thu, 25 May 1989 09:23
21 lines
1246 bytes
1246 bytes
Is there an easy fix for ARexx's current-directory problem (not giving it
to the ARexx process when RX is run)? I know you could just pass the
current directory to the script as an argument, but that looks bad and
seems messy and is slow. Does WShell fix this? Would it be possible to
write a replacement for the RX command which would pass the current
directory? (I'll try making one if nothing easier and better comes up.)
Please E-MAIL only. (Unless mail doesn't go through, of course.) I'll post
a summary. Also, if this has been discussed before, forgive me, I just got
back on Usenet less than a month ago.
Thanks in advance.
Bryan
--
______________________________________
_/ Bryan Ford - bryan@chroma.inland.com \_
_/ ..!utah-cs!caeco!i_core!chroma!bryan \_
/ ..!uunet!iconsys!caeco!i_core!chroma!bryan \
Technical Details
Message-ID:
<0667.AA0667@chroma>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!iconsys!caeco!i_core!chroma!bryanShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!iconsys!caeco!i_core!chroma!bryan From: bryan@chroma.UUCP (Bryan Ford) Newsgroups: comp.sys.amiga.tech Subject: ARexx current directory woes Summary: Is there an easy fix? Message-ID: <0667.AA0667@chroma> Date: 25 May 89 09:23:34 GMT Followup-To: comp.sys.amiga.tech Lines: 21