Path: utzoo!utgpu!water!watmath!clyde!bellcore!faline!thumper!ulysses!andante!princeton!udel!gatech!emcard!fedeva!csun!csuna!acphssrw
From: acphssrw@csuna.UUCP
Newsgroups: comp.sys.amiga.tech
Subject: Re: ARexx Questions
Summary: "shell -c <shell commands>"; ARexx without WShell a bit crippled
Message-ID: <1267@csuna.UUCP>
Date: 30 Jun 88 20:13:23 GMT
References: <2119@cadovax.UUCP> <4131@cbmvax.UUCP> <417@ardent.UUCP>
Reply-To: acphssrw@csuna.UUCP (Stephen R. Walton)
Organization: California State University, Northridge
Lines: 22


Rob Peck wonders how to make the Dillon Shell do a script from an
Execute() call.  The answer is that the Shell has both the "source"
command and the "-c" command line switch, so that:

Execute("shell -c source script-file",0,0);

will work fine.

This brings up something else: if you're going to do a lot of this
kind of thing (doing CLI stuff from ARexx scripts), you probably want
to buy ConMan and/or WShell.  ConMan manages the input stream so that
one can use the ARexx PUSH and QUEUE commands to put CLI commands on
your CLI window's input stream.  WShell gives you the ability to
overcome many of the limitations of Execute(), such as searching the
path.  I normally keep non-CBM commands in a directory other than C:,
where ARexx's ADDRESS COMMAND (which does Execute()'s in the absence
of WShell) won't find them unless I hard-wire an explicit path into my
scripts. 

Stephen Walton, representing myself		swalton@solar.stanford.edu
Cal State, Northridge				rckg01m@calstate.BITNET