Hello Michael!

31 Jul 23, Stas Mishchenkov wrote to Michael Dukelsky:

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?

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Kai,

Tuesday September 19 2023, Kai Richter wrote to Michael Dukelsky:

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? ;-)

It was fixed in hptlink in February AFAIR.

Btw, is the config file detection part of every individual module or
is it a centralized fidoconfig function?

It is defined in fidoconfig library and used by all programs.

Michael

... node (at) f1042 (dot) ru
--- GoldED+/LNX 1.1.5-b20230926
* Origin: Moscow, Russia (2:5020/1042)