Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!munnari.oz.au!labtam!eyrie!walking!david
From: david@walking.pub.uu.oz.au (David Le Blanc)
Newsgroups: comp.sys.amiga.tech
Subject: wb2 rexx
Message-ID: <1854bb07.ARN1736@walking.pub.uu.oz.au>
Date: 8 Dec 90 18:45:47 GMT
Reply-To: david@walking.pub.uu.oz.au
Followup-To: comp.sys.amiga.tech
Organization: PizzaLovers INC.
Lines: 34

While 'playing' with wb202 I noticed that 'rexx' scripts are executed
relative to their current directory, not yours.

Eg
/*
 * Script to run vi in the background
 */

parse arg param

address COMMAND

'changetaskpri 0'
'cd'
'run bin:z' param

The 'cd' command displays the path of the 'rexx:' directory, not your current
directory. HENCE, to use the script, you must pass the full PATH of the
file to be edited, not just the name.

Also, does anyone know if W.Hawes is working on an even better WShell? He
should (IMHO), since WShell is pretty much defunct with Wb2.0 ie (no access
to the 2.0 internally resident commands, file completion wont work unless
you use conman, but conman is now lacking in features compared to the new
console. (ALMOST everything that made it better has been implemented.
I still think it has a much superior line editor though. And I crave the
command line rexx thingies "do for 10; 'sound mmd'; end" :-))

 ----------------------------------------------------------------------------
    David Le Blanc    UUCP (home)   : eyrie!walking!david@labtam@munnari.oz
    david@walking     ACSNET (work) : david@dogmelb.dog@munnari.oz
                                      CSIRO Division of Geomechanics
    "Life? Dont talk to ME about life.. " :  Marvin the paranoid android.
 ----------------------------------------------------------------------------