CompuServe Messages

Many thanks to you and Vic and Bob… the thought of an indirection such as CCBIN: in the middle of the path made lightbulbs flash over my head, but in reading Vic's message, I would tend to believe that the path gets locked at the time it's instantiated, meaning a subsequent re-assignment of CCBIN: would have no effect. We do run a WShell and ARexx environment at Syndesis, so Bob's trick might work out, too. From your statement, you're saying that PathMan re-evaluates any logical assignment every time it's accessed, or is it more like AmigaDOS PATH in that the assignment is "frozen" at the moment that particular CLI is launched? We don't run PathMan. It always made me kind of nervous, although I'm sure it shouldn't. Like, if I write to one of those extended assignments, where does the file get made? Is that well-defined?