Wilfred van Velzen wrote:

WVV>  TK> Not a big deal, but perhaps windows version should write "\"
WVV>  TK> and linux version "/" to those export files. :)
WVV>
WVV>  TK> grep fmail_help areas.*
WVV>  TK> areas.bbs:!\bbs\fmail\msgbase\jam\fmail_help FMAIL_HELP
WVV>  TK> 2:221/6 areas.gld:AREADEF FMAIL_HELP "FMAIL_HELP" A Echo JAM
WVV>  TK> /bbs/fmail/msgbase/jam/fmail_help 2:221/6.600 (Loc)
WVV>
WVV> Those files can be written by 2 of the modules when auto export is
WVV> executed. FConfig (which only exists as a Windows program), and
WVV> 'FTools addnew -A'. I don't use the latter, but I think you might?

Yes, I do use 'ftools addnew -A'.

WVV> How is that path in your configuration? As a linux or as a windows
WVV> version?

I run Fmail/Ftools only in linux. FConfig only in windows :D.

All paths in FConfig are in windows format:

ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
³ Area name    FMAIL_HELP
³ Comment      FMAIL_HELP
³ JAM MB name  \bbs\fmail\msgbase\jam\fmail_help

If I try to enter "/", FConfig will change it to "\".

WVV> What I do, is have all my paths in windows form, and use the
WVV> FMAIL_REPLACE_DRIVE environment variable for the linux modules.
WVV> And I have a little python script that converts the windows paths
WVV> in areas.gld to linux paths...

Of course I also made the conversion  "\" -> "/" in my converter. Also
in linux Golded.cfg I have "mappath \ /".

But it was strange that at the same time areas.bbs and areas.gld have
different separator. :)

'Tommi

--- FMail-lnx64 2.1.5.0-B20230106