CompuServe Messages

Mike, I think the gun is the right approach. <grin> Trying to parse lines that contain file names is sure a mess when the names can include spaces. I seem to remember Bill adding a paramter to some of the functions that return lists of names so that you can specify a different separator, such as ';'. This makes the parsing a lot easier for those commands. I don't remember the specifics – you should probably take a look at the documentation updates that Bill ships on the ARexx distribution disks. One trick that I use alot for wild-card expansion is to issue a "list pat xxxx quick nohead" CLI command from my ARexx script, and pipe the output from list to "execio stem foo." – this only works if you have WShell as well as ARexx. What this does is to take the standard-output from the list command and place the lines into the stem variable foo – foo.0 will contain the number of lines of text contained, and foo.1 thru foo.n will contain the lines of the command output. In this case (the list command), each line will be a single file name (and the included space is no longer a problem). Hope this helps…. …BobR