open https://gitlab.synchro.net/main/sbbs/-/issues/357

I have configured ddfilelister for use in 'New file scan' as per the readme, so the config line in my shell looks like this...```cmdkey N print "\r\n\1c\1hNew File Scan\r\n" exec "?../xtrn/ddfilelister/ddfilelister.js -MODE=new_file_search" end_cmd```I then select 'All areas' when prompted.It will correctly show the new files. So far so good.However, I then exit with 'Q' but the pointers for the file areas are NOT updated. So if I perform another New scan, I get the same results.Is there an automatic way for the pointers to get updated when doing this?
--- SBBSecho 3.14-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/357#note_2391

ddfilelister can (and arguably should) do this after the user does a new-file scan. This was an oversight. I can update ddfilelister to do this when the user does a new-file scan.
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/357#note_2392

Actually, as far as I can tell, there are no scan pointers for the filebases. The new file scan is based on the user's last file scan time; ddfilelister already updates the last scan time when the user does a new file scan (though that isn't saved directly to the user's last scan time yet).When you say you get the same results when you do another scan, are you logging off and back on again before you do a new scan, or do you do the new scan in the same session? My understanding is that Synchronet doesn't actually save the user's last file scan time until the user logs off, so you should see different results once you log off and log in again.
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/357#note_2400

OK, this makes sense, and means this is working as expected.I'm working if this should pivot to a request for Synchronet to actually update Last File Scan times _immediately_, in the same way it does for Message File Areas?
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/357#note_2402

If Synchronet changes that, then I'd also have to update my file lister accordingly.
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/357#note_2404

I find that users frequently want to "re-list" the new files, so the "new file" date/time used for comparison isn't updated (stored to the user's record) until log-off. This is how Synchronet has always operated and pretty how its been documented (https://synchro.net/docs/user.html#NewFileScan) as well, so I see no reason to change this behavior now. I think WWIV and its derivatives (e.g. Renegade, etc.) all behave in the same/similar way.
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/357#note_2405

Fair enough - if that's 'the way it should be' seems sensible to just close this one off.Thanks for the input, gentlemen!
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

close https://gitlab.synchro.net/main/sbbs/-/issues/357
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)