Subj : Re: Badareas.lst location
To : Digital Man
From : Gamgee
Date : Thu Sep 25 2025 01:51 pm
-=> Digital Man wrote to Gamgee <=-
DM> Re: Re: Badareas.lst location
DM> By: Gamgee to RickV on Thu Sep 25 2025 09:19 am
> Digitalman - seems like this is a bug to me. The function in SCFG is
> not reading the defined location of 'badareas.lst' and seems hard-wired
> to ../data/badareas.lst .
DM> That's just the default value in the input dialog; typing a different
DM> value overrides the default.
Okay, understood.
DM> Yes in theory, SCFG could read the sbbsecho.ini file to find whatever
DM> path/filename the sysop chose to name that file. However, a sysop can
DM> create/use multiple sbbsecho configuration files (they don't have to be
DM> ctrl/sbbsecho.ini), so SCFG wouldn't magically know how to find any
DM> other non-default SBBSecho config files.
That seems a pretty niche use-case - I'd guess that VERY few sysops are
using multiple sbbsecho.ini files. If somebody *was*, then yes I could
see how they might need to type in a new value in the input dialog to
import that badareas.lst into SCFG. But for the other 99% ...? To be
fair - I see ZERO reason to change it from the default location anyway.
I guess my question then is - does the location specified in
sbbsecho.ini for the badareas.lst file actually make that file get
created/updated in the location specified? Or will it always go to
../data ?
DM> If you think it's a bug, file a bug report.
I don't have the issue myself, and use the default location for
badareas.lst ... was just conversing with the OP. I will let him worry
about a bug report, if he desires. :-) Thanks.
