CompuServe Messages

Ed, no trick that I can help you with. Actually, SETENV [name] [string] will exactly work like ECHO [string] TO ENV:[name], and GETENV [name] will work exactly like TYPE ENV:[name]. So, in [name], you may give an additional path. Whereas $<variable> in the command line will be substituted by the shell process, which scans the given <variable> and will stop the scanning when the first character out of the range [0..9|a..z|A..Z] is encountered. Try the following example to proof this: setenv x single x setenv x.x double x getenv x getenv x.x ;;;; fine ! echo $x echo $x.x ;;;; oops ! So there ist no way to give a path name in <variable>, because only the part before the slash is taken as the name of the variable and the rest is truncated. A multiple assign of ENV: won't help, either. The only work-around I know of is (WB 2.1/3.0) echo `getenv x.x` ;;;; mmmh ! – wkc – … via AP from Hamburg, Germany