With reference to '[md-2] Re: Bulk Attachments' by Patrick Ford

> . . .starts it. But that is logically exactly the same place, and the same
> file.
> Has rx a limitation on path length? If so, maybe it's running into that even
> after a path short enough to start it is supplied.

  It could be that the interpreter expands the path internally, but I'm
getting out of my depth, so I'm returning to the 3'6" end.  :-)

Patrick, in another list you asked about a script which would output the
command set of an MUI programme, this is mine, give it a go.

-- 8< -- Cut Here -- 8< --
/*
ARexx Commands form an MUI programme.
Jules <[EMAIL PROTECTED]>

USAGE rx ARexxMUICommands.rx ARexxPortName
>From a shell:
 (no quotes around the port-name)
 (port-names are case sensitive)
 WB: rx REXX:ARexxMUICommands.rx MD.1

A list of commands is output to RAM:
*/

OPTIONS RESULTS
PARSE ARG MUIPORT
MUIPORT=STRIP(MUIPORT)
IF ~SHOW('P',MUIPORT) THEN EXIT
ADDRESS (MUIPORT)
AA=POS('.',MUIPORT)
IF AA>1 THEN MUIPORT=DELSTR(MUIPORT,AA)
HELP 'RAM:'||MUIPORT||'_CmdSet.txt'
EXIT

-- 8< -- And Here -- 8< --

-- 
Regards
  Jules
-- 
I will not Xerox my butt
-- Bart Simpson
__________________________________________________________________
MicroDot-II Mailing List - http://www.vapor.com/md2/
MicroDot-II FAQ: http://faq.vapor.com/md2/
Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP
Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE

Reply via email to