Subj : A bracket or two...
To : Steve Quarrella
From : Paul Quinn
Date : Thu Oct 26 2000 03:30 pm
Hi! Steve,
On 25 Oct 00 14:10, Steve Quarrella wrote to Paul Quinn:
PQ>> It would be nice to be able to refer to DOS environment variables,
PQ>> again. Any clues, please?
SQ> If you have something like SET FOO=C:\BAR, can't you do something
SQ> like $FOO in the appropriate field, which FE will then interpret as
SQ> C:\BAR?
You had me going there for a few minutes.<sfx: wags finger> I thought maybe I
had read the help/dox incorrectly and was suffering under the delusion the
brackets were required, when they weren't really.
The on-line help says (in part):
-----8<-----C-U-T--H-E-R-E----->8-----
A special feature of FastEcho is that macros like
'$[FD]' can be used. These macros will be translated at
run-time using the current definition of the specified
environment variable. For example $[FD]NETMAIL with SET
FD=C:FRODO will be expanded to C:FRODONETMAIL at
run-time.
-----8<-----C-U-T--H-E-R-E----->8-----
My FeSetup.Exe refuses to accept the bracket characters, absolutely. My setup
used to work, but now 5 years later I don't use a FrontDoor mailer or even a RA
BBS any more, so, my DOS paths are all different. The paths have to be
hardcoded instead of being flexible... for each node/task.
Does yours accept brackets? Anynoe else's? Or is it a FAQ and there's some
sort of fix for it?
Cheers,
Paul.
--- BT-W32 2.60XEg6/BinkD-W32 0.9.4
* Origin: Quinn's Post, node 2 - Maryborough, Qld, OZ (ZMH only) (3:640/384)
