hptlink/lnx 1.9 2023-01-07
Usage: hptlink [options] [areaname ...]
Options: -t - build reply TREE
Please update. :)
=== Cut ===
hptlink/lnx 1.9 2023-02-24
Usage: hptlink [options] [areaname ...]
Options:
-c <config> - config file
As usual, you need to provide the path to the configuration file
either in the FIDOCONFIG environment variable, or with the "-c"
option.
If neither "-c" command line option, nor FIDOCONFIG environment
variable is defined, then the fidoconfig location is given by CFGDIR
and CFGNAME defined in huskymak.cfg during compilation.
$ hptlink -t crimea.talk hptlink/lnx 1.9 2023-01-07
Could not find Config-file
Would you be so kind to add "-c" option?
As usual, you need to provide the path to the configuration file
either in the FIDOCONFIG environment variable, or with the "-c"
option.
Some mails before:
If neither "-c" command line option, nor FIDOCONFIG environment
variable is defined, then the fidoconfig location is given by
CFGDIR and CFGNAME defined in huskymak.cfg during compilation.
I think that's a good usual default.
$ hptlink -t crimea.talk hptlink/lnx 1.9 2023-01-07
Could not find Config-file
Would you be so kind to add "-c" option?
And fix the usual default config detection first? ;-)
Btw, is the config file detection part of every individual module or
is it a centralized fidoconfig function?
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 1,114 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 492514:10:32 |
| Calls: | 14,267 |
| Calls today: | 3 |
| Files: | 186,320 |
| D/L today: |
26,988 files (8,775M bytes) |
| Messages: | 2,518,462 |