TID: FMail-lnx64 2.1.5.2-B20230114
RFC-X-No-Archive: Yes
TZUTC: 0100
CHRS: UTF-8 2
PID: GED+LNX 1.1.5-b20161221
MSGID: 2:280/464 63d3ac4c
REPLY: 2:221/6.0 63d37fc6
Hi Tommi,

On 2023-01-27 09:39:50, you wrote to me:

 TK> I was writing a small converter from fmail to smapinntpd and I noticed
 TK> that areas.bbs and areas.gld are using a different directory
 TK> separator.

 TK> Not a big deal, but perhaps windows version should write "\" and linux
 TK> version "/" to those export files. :)

 TK> grep fmail_help areas.*
 TK> areas.bbs:!\bbs\fmail\msgbase\jam\fmail_help FMAIL_HELP 2:221/6
 TK> areas.gld:AREADEF FMAIL_HELP "FMAIL_HELP" A Echo JAM
 TK> /bbs/fmail/msgbase/jam/fmail_help 2:221/6.600 (Loc)

Those files can be written by 2 of the modules when auto export is executed.
FConfig (which only exists as a Windows program), and 'FTools addnew -A'. I
don't use the latter, but I think you might?

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

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


Bye, Wilfred.

--- FMail-lnx64 2.1.5.2-B20230114
 * Origin: FMail development HQ (2:280/464)
SEEN-BY: 1/123 10/0 1 15/0 90/1 102/401 103/1 705 105/81 106/201 120/340
SEEN-BY: 123/131 124/5016 129/305 153/757 7715 154/10 203/0 214/22
SEEN-BY: 218/0 1 109 215 650 700 720 840 860 870 880 900 221/0 226/30
SEEN-BY: 227/114 229/110 111 112 113 114 206 307 317 424 426 428 470
SEEN-BY: 229/550 664 700 240/1120 5832 266/512 280/464 5003 5555 282/1038
SEEN-BY: 292/854 8125 301/1 310/31 317/3 320/219 322/757 341/66 234
SEEN-BY: 342/200 396/45 423/120 460/58 633/280 712/848 770/1
PATH: 280/464 103/705 218/700 229/426