> I suspect it is, or was, to avoid getting notified by Geany's own changes to > the files. This might have been fixed since then, or there might be a better > fix.
I thought that, but it shouldn't be a problem with local disks since the OS controls mtime. IIUC there used to be a problem with network file systems since they use the server time for mtime, but if the server hadn't finished writing the file when the application did what Geany does and stats to get the timestamp shortly after a close, the stat gets the clients idea of mtime and the servers was likely later (newer). But would trigger the message on the next stat when the client had updated its time, so it can't be for that. And at least on Linux and NFS thats now fixed by forcing a sync with the server before a stat is returned, so mtimes are the same, don't know about Samba. Or maybe in its really really early life (I didn't go back in history past ten years but I have a vague memory) the system time was used for the timestamp after save instead of statting the file again, it would always be newer or the same as the disk time so equals wouldn't work. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2133#issuecomment-488967009
