Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    MAKENL_NG    |    MakeNL Next Generation.    |    1,725 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 1,111 of 1,725    |
|    Ulrich Schroeter to Janis Kracht    |
|    MakeNL v3.4.1 Release    |
|    03 Jan 14 21:14:30    |
      Hi Janis,              Friday January 03 2014 13:44, you wrote to me:               JK> Hi Uli!        >>> Hi Ward,        >>>>> Discussions are underway on dealing with Marc's other issue with        >>>>> MakeNL; he feels that there should not be an age limit on        >>>>> segments. The original Ben Baker version of MakeNL would only go        >>>>> ...               >> so there are some advantages and disadvantages of each processing        >> method that makenl offers               JK> Yes, I can see that. I'll mention this to Marc Lewis, R19C. It may        JK> be his whole problem with makenl not 'seeing' older segments.               JK> Let's hope :)              on tests with the makenl_ng I had an older copy of my live working directory       for makenl on another disk. After some bugfixings, that tooks a while, I've       copied the new makenl.exe to the test disk and was still wondering, why the       new makenl did not found any of the existing segments :-P              As Ward mentions about "old" segments ... I've also 2 "older" segment files in       my working directory, so they've been never found, once got aware about the       strict file extension numbering schema ...       later Ward reported, some other issues and I've tried to reproduce       the scenario, but couldn't find the trigger ...       after several mails forth and back, the only difference was the       segments definition schema Ward used and I've used to reproduce the issues.              As the definition with .* changes the file search routine completely, and I've       fixed the definitions in my test environment, I've also could reproduce the       issues Ward reported       All in all, it was still trial and error until we've got it fixed.              section 3.2 Generic File Name and 3.3 Explicit Filename and 6.3.6 CLEanup       in makenl's docu gives some info, but no info how makenl       switches between 2 process modes dependent of the makenl.config definition       and under which circumstances the update of file extensions of segment files       will happen in the working directory :-P              Probably we should create a FAQ for makenl_ng with all found issues and       their related answers ;)                             JK> Take care,        JK> Janis        JK> $ Origin: Prism bbs (1:261/38)              regards, uli ;-)              ---        * Origin: AMBROSIA - Frankfurt/Main - Germany (2:240/1120)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca