Hi! All,

Is it just my configuration or does the FE 1.46 FeSetup.Exe really _not_ allow the brackets '[]' to be used? It's been bugging me ever since the problem presented itself here (since '97?)

It would be nice to be able to refer to DOS environment variables, again. Any clues, please?

Cheers,
Paul.

--- BT-W32 2.60XEg6/BinkD-W32 0.9.4
* Origin: Quinn's Post, node 5 - Maryborough, Qld, OZ (ZMH only) (3:640/384)

It would be nice to be able to refer to DOS environment variables,
again. Any clues, please?

If you have something like SET FOO=C:\BAR, can't you do something like $FOO in the appropriate field, which FE will then interpret as C:\BAR?

---
* Origin: Where'd you get the gun, John? (1:393/9005)

Hi! Steve,

On 25 Oct 00 14:10, Steve Quarrella wrote to Paul Quinn:

It would be nice to be able to refer to DOS environment variables,
again. Any clues, please?

If you have something like SET FOO=C:\BAR, can't you do something
like $FOO in the appropriate field, which FE will then interpret as 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)

If you have something like SET FOO=C:\BAR, can't you do something
like $FOO in the appropriate field, which FE will then interpret as
C:\BAR?

You had me going there for a few minutes.<sfx: wags finger> I

Your RTFM is better than my memory. Nope, I can't insert the brackets here, either, and what I suggested plain out doesn't work. I'll forward this to Tobias, although I'm not optimistic about hearing from him about it.

---
* Origin: Where'd you get the gun, John? (1:393/9005)

Hi! Steve,

On 27 Oct 00 18:03, Steve Quarrella wrote to Paul Quinn:

If you have something like SET FOO=C:\BAR, can't you do something
like $FOO in the appropriate field, which FE will then interpret as
C:\BAR?

You had me going there for a few minutes.<sfx: wags finger> I

Your RTFM is better than my memory. Nope, I can't insert the
brackets here, either, and what I suggested plain out doesn't work.
I'll forward this to Tobias, although I'm not optimistic about
hearing from him about it.

Ahh, even that sort of response is great news. :) At least now I know the problem is repeatable and not just in my config.

Thanks for your help, Steve.

Cheers,
Paul.

--- BT-W32 2.60XEg6/BinkD-W32 0.9.4
* Origin: Quinn's Post, node 5 - Maryborough, Qld, OZ (ZMH only) (3:640/384)

Hello Paul!

26 Oct 00 22:30, Paul Quinn wrote about A bracket or two... to Steve Quarrella:

You had me going there for a few minutes.<sfx: wags finger>

Me too! ;-)

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.

I had a look at my setup (first time for a year or so), and found that EVERYTHING was written in full! I tried to enter the macros in the form listed
in the on-line help, but haven't yet found a way to get the '[' and ']' to be entered in the field on the FESETUP->SYSTEM->PATHNAMES screen. I have also tried the ALT-??? trick as well, along with a number of other potential varients on the theme gleaned from the docs/setups of other programs.

Does yours accept brackets? Anynoe else's? Or is it a FAQ and
there's some sort of fix for it?

I can report mine doesn't, I do run Intermail 2.29g (FD compatible) and EleBBS in a DOS 6.22 environment with a characterset codepage of 437. I'm looking forward to hearing the definitive answer to this question, and trying any suggestions.

Using environment variables can help reduce the logistics of moving things around, which happens occasionally when resources change.

Take care...

Chris
Sysop of the Luton Area BBS (+44-1582-752462 24 Hours)

... I am in total control, but please don't tell my wife.
---
* Origin: Luton Area BBS +44-1582-655790 - Speeds to 28800BPS (2:257/144)

Hi! Chris,

On 29 Oct 00 02:30, Chris Lander wrote to Paul Quinn:

the form listed in the on-line help, but haven't yet found a way to
get the '[' and ']' to be entered in the field on the FESETUP->SYSTEM->PATHNAMES screen. I have also tried the ALT-???

Yep that's it!, that's the problem alright. That's a neat trick with the ALT-??? keys; I can't remember if I tried that. I think I tried using an editor (not hex), carefully trying to keep the number of chars for that field the same but that didn't work. Maybe there's a checksum of some sort for each field in FeSetup?

Maybe the 'fix' will be to use the FE 1.45 FeSetup.<shrug> Let's see what else
turns up in the echo. I'm hanging out for a comment from Mark Lewis (1:3634/12); I know he uses FE and environment variables pretty heavily.

I can report mine doesn't, I do run Intermail 2.29g (FD compatible)
and EleBBS in a DOS 6.22 environment with a characterset codepage of
437. I'm looking forward to hearing the definitive answer to this question, and trying any suggestions.
Using environment variables can help reduce the logistics of moving things around, which happens occasionally when resources change.

Ahh, yes; exactly. I've turned using environment variables into an art form, even to the point of using/re-using their values, as appropriate, to create ASCII config files on-the-fly from my batch files for such things as the BinkD TCP/IP mailer, and for a 'Squish' config file (and others). I even selected this editor since its config file can utilize environment variables (and the FE
config file for echo area definitions).

Let's see what else turns up...

Have fun! in the meantime.

Cheers,
Paul.

--- BT-W32 2.60XEg6/BinkD-W32 0.9.4
* Origin: Road Kill on the Information Super Dirt Road (ZMH only) (3:640/384)

[using environment variables in FEsetup]

Maybe the 'fix' will be to use the FE 1.45 FeSetup.<shrug>
Let's see what else turns up in the echo. I'm hanging out for
a comment from Mark Lewis (1:3634/12); I know he uses FE and
environment variables pretty heavily.

(sadly) i have to report that i had to 'hardcode' everything in FE... i will, however, confirm that this bug was reported on Dec 30, 1997 in the beta echo...
no word from tobias, though...

)\/(ark


* Origin: (1:3634/12)