Hello Bj÷rn!

09 May 18 05:38, you wrote to me:

 BF> I'm sorry to hear that. The last version I left behind was 3.141 -- I
 BF> was working my way down PI...  8-)

 What make you so shure that everything that is commented about, was not
 in 3.141.  Some bugs/features only show up later, when ways of use change.

 BF>    Well, *my* last contribution worked the same with MSDOS, Windows, unix,
 BF> linux, Amiga SAS and a lot of other OSs that I cant remember, but my make
 BF> file was written in cooperation with Jamnntp author Johan Billing, and we
 BF> spent a lot of time to create one single, universal make file that would
 BF> work on almost any environment.

 In normal use, what I am talking about, does not surface. How can you be
 sure, that your test environment covered, all exceptions.?

 BF>    Once again, I'm sorry to hear that the guys that took over Johan's
 BF> and
 BF> mine project lost some, if not all, that universal functionality.

 Sorry I do not agree with you.

 KvE>> a file is file name. Most region updates are distributed as
 KvE>> filename.XXX where XXX is the daynumber for the coming friday.

 BF>    And that, in my mind, is a huge mistake. Ever since I first used MakeNl
 BF> as 2:203/0 in 1991 (I think) I've always used the password.UPD approach.
 BF> It wasn't until I became RC20 that I had to start using the daynumber
 BF> approach. Alas, I've only had a few glitches along the way, but I still
 BF> think that the password approach is much safer.

 Not using nnnn.upd, may be a big mistake. The sample config files use and
 produce files with a daynumber suffix.

 KvE>> But that does not matter, it
 KvE>> will be put in the master directory with the daynumber of the the
 KvE>> publishing day.

 BF>    So what?

 Your comments show, that you have never used makenl to produce daily
 nodelists.

 KvE>> In windows as well a in Unix, you can use filename.upd or whatever.
 KvE>> What makenl will do with when it is moved to the master directory,

 BF>    It's not moved to the main directory if you configure it properly, it's
 BF> moved to this directory:

 BF> update .\tmp

 Yes and from update .\tmp it is moved to the master directory.

 KvE>> is as above,
 KvE>> dat the daynumber of the publishing day. So you get a file with the
 KvE>> name: filename.upd.128 if today was the publishing day.

 BF>    ???  I've never ever seen something so outlandish a hypothetical
 BF> situation happening here.

 Good for you, I have.

 KvE>> What happens in windows/dos, is the OS cannot handle two dots in a
 KvE>> filename

 BF>   Of course Windows, as well as it's DOS emulation, can handle two dots! I
 BF> have media files that have more than a dozen dots in them. How long ago
 BF> was it that you used Windows...?  8-)

 O.K. I just tried it, you win.

 KvE>> If it should work as you say, then there
 KvE>> is a definit bug in the makenl code.

 BF>    If that is so, the bug must have been introduced after I left it. But I
 BF> highly doubt it, because that part of the code should never need to be
 BF> changed IMHO.

 KvE>> Well I did, and using a * in the CTL file as some do, also creates
 KvE>> havoc on systems that do not limit how the filename is structured.

 BF>    Well, *that* does not surprise me a bit. I bet that option is not in
 BF> the default config file or the DOC file

 Indeed it is not, but I believe it is used.

Kees

--- GoldED+/LNX 1.1.5
 * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)