2015-07-29 12:05 GMT+05:00 Михаил Гаврилов <mikhail.v.gavrilov(a)gmail.com>om>: Of course making this check by timer extremely wasteful especially if the file size more than megabyte. So it is better to do it at the request of the user, namely, when the user saves the changes.

2015-07-29 13:13 GMT+05:00 Lex Trotman <elextr(a)gmail.com>om>: Algorithm: 1. user open file a) calculate CRC for opened file and store into memory 2. user try save file a) calculate CRC for file which would be replaced b) compare two CRC c) if CRC are different notify user that someone had changed the file and suggest merge changes with merge tool d) if CRC is identical just replace file on disk. That would be really very convenient than it is now. -- Best Regards, Mike Gavrilov.

Oh... I think is not good idea identifies that the file changed a few tens of seconds after it happens. For example I watch log file which is really changed every second. Notification every tens of seconds would be very annoying. Another case two developers edited source file directly. Of course be better use here version control but my suggestion also can help here solve conflicts. -- Best Regards, Mike Gavrilov.

Maybe I'll surprise you but Geany on GNU Linux the best GUI tool for viewing logs . Cause Geany much faster than Gedit and Sublime, not to mention the other heavier editors. Maybe I'll surprise you and here, but do not always want to deploy a full-fledged CSV for quick editing files directly on the server. Sorry to trouble you, if you did not like my suggestion.

On 29 July 2015 at 19:42, Михаил Гаврилов <mikhail.v.gavrilov(a)gmail.com> wrote: Yes, thats why Geany 1.25 has changed the notification to a bar at the top of the editor, it is only visible when you have the file visible and it is not modal so it can be ignored if you want to. But if you have the log file visible, I would have thought you would want to know there is more information available. The current modification time system is to alert users to things like someone else modifying a file you have open, or when checking out a version from VCS changes the file. That way you are more likely to make edits to the right version of the file.

On 29 July 2015 at 22:34, Михаил Гаврилов <mikhail.v.gavrilov(a)gmail.com> wrote: Well, in many applications they do, but thats irrelevant. I'm afraid so, it is very unlikely that we will remove checking for a file change, only improve it. We might accept a well written PR that allowed a user to turn modification checking off per-file, so you can set your log to not annoy you. Similarly a PR to calculate and use signatures to check for a changed file at save *if the timestamp says its changed* might be acceptable if it has an option to turn it off. Cheers Lex