Hi!
I would suggest check differences between edited and saved file at the saving process. It would be more correct to compare the checksum file before changing and the checksum saved file, so could accurately determine that someone had changed the file, and if file would be saved this changes may be loose. I would suggest to launch differ tool such as meld for merge these changes.
-- Best Regards, Mike Gavrilov.
Could you provide please some cases/examples, in which default behaviour works wrong?
On 28 July 2015 23:26:21 GMT+03:00, "Михаил Гаврилов" mikhail.v.gavrilov@gmail.com wrote:
Hi!
I would suggest check differences between edited and saved file at the saving process. It would be more correct to compare the checksum file before changing and the checksum saved file, so could accurately determine that someone had changed the file, and if file would be saved this changes may be loose. I would suggest to launch differ tool such as meld for merge these changes.
-- Best Regards, Mike Gavrilov. _______________________________________________ Users mailing list Users@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/users
2015-07-29 11:59 GMT+05:00 Vit Ry frodox@zoho.com:
Could you provide please some cases/examples, in which default behaviour works wrong?
There are many different cases when the time will be different, but the content is not.
If main task before saving file notify user that someone else had to edit this file is my proposed solution with comparing checksum much safer.
Running utilities for merge optional but recommended in such cases.
2015-07-29 12:05 GMT+05:00 Михаил Гаврилов mikhail.v.gavrilov@gmail.com:
2015-07-29 11:59 GMT+05:00 Vit Ry frodox@zoho.com:
Could you provide please some cases/examples, in which default behaviour works wrong?
There are many different cases when the time will be different, but the content is not.
If main task before saving file notify user that someone else had to edit this file is my proposed solution with comparing checksum much safer.
Running utilities for merge optional but recommended in such cases.
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.
On 29 July 2015 at 18:04, Михаил Гаврилов mikhail.v.gavrilov@gmail.com wrote:
2015-07-29 12:05 GMT+05:00 Михаил Гаврилов mikhail.v.gavrilov@gmail.com:
2015-07-29 11:59 GMT+05:00 Vit Ry frodox@zoho.com:
Could you provide please some cases/examples, in which default behaviour works wrong?
There are many different cases when the time will be different, but the content is not.
If main task before saving file notify user that someone else had to edit this file is my proposed solution with comparing checksum much safer.
Running utilities for merge optional but recommended in such cases.
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.
It would also have to be done when the file is opened, otherwise you have nothing to compare against.
This is likely to make opening and closing large numbers of files slow.
Cheers Lex
Users mailing list Users@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/users
2015-07-29 13:13 GMT+05:00 Lex Trotman elextr@gmail.com:
It would also have to be done when the file is opened, otherwise you have nothing to compare against.
This is likely to make opening and closing large numbers of files slow.
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.
On 29 July 2015 at 18:27, Михаил Гаврилов mikhail.v.gavrilov@gmail.com wrote:
2015-07-29 13:13 GMT+05:00 Lex Trotman elextr@gmail.com:
It would also have to be done when the file is opened, otherwise you have nothing to compare against.
This is likely to make opening and closing large numbers of files slow.
Algorithm:
user open file a) calculate CRC for opened file and store into memory
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.
This could handle identifying that the underlying file has changed at save time, but currently Geany identifies that the file changed a few tens of seconds after it happens. Then it is more convenient for the user to do something about it, rather than doing a large editing session then finding there is a problem.
-- Best Regards, Mike Gavrilov. _______________________________________________ Users mailing list Users@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/users
This could handle identifying that the underlying file has changed at save time, but currently Geany identifies that the file changed a few tens of seconds after it happens. Then it is more convenient for the user to do something about it, rather than doing a large editing session then finding there is a problem.
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.
Am 29.07.2015 um 11:42 schrieb Михаил Гаврилов:
This could handle identifying that the underlying file has changed at save time, but currently Geany identifies that the file changed a few tens of seconds after it happens. Then it is more convenient for the user to do something about it, rather than doing a large editing session then finding there is a problem.
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.
Geany is an editor, not a log viewer. So please understand that that use case has lower priority to us.
You could write a plugin that auto reloads every 0.5s or so, then you should never see the notifcation (conceptually, not considering dodgy behavior on remote file systems).
And no editor can help against two (or more) developers shooting each other in the foot by editing the same file.
Best regards
Geany is an editor, not a log viewer. So please understand that that use case has lower priority to us.
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.
And no editor can help against two (or more) developers shooting each other in the foot by editing the same file.
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.
Am 29.07.2015 um 14:31 schrieb Михаил Гаврилов:
Geany is an editor, not a log viewer. So please understand that that use case has lower priority to us.
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.
This is nice (and so true) but it's still not the primary use case.
Best regards
On 29 July 2015 at 19:42, Михаил Гаврилов mikhail.v.gavrilov@gmail.com wrote:
This could handle identifying that the underlying file has changed at save time, but currently Geany identifies that the file changed a few tens of seconds after it happens. Then it is more convenient for the user to do something about it, rather than doing a large editing session then finding there is a problem.
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.
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.
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.
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.
-- Best Regards, Mike Gavrilov. _______________________________________________ Users mailing list Users@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/users
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.
To be honest it's annoying before, I just endure it. In any case, there is always the button to re-read the contents of the file. And frequent notifications annoying once again.
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.
Imagine that-be if each database when showing query result notified that visible data are not relevant.
First it would be very costly in terms of resources. Second on the tables with frequents inserts notifications will be blinks.
In general, I understand that I am not convincing. But the editing files is not a "chat" and not needed online here.
On 29 July 2015 at 22:34, Михаил Гаврилов mikhail.v.gavrilov@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.
To be honest it's annoying before, I just endure it. In any case, there is always the button to re-read the contents of the file. And frequent notifications annoying once again.
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.
Imagine that-be if each database when showing query result notified that visible data are not relevant.
Well, in many applications they do, but thats irrelevant.
First it would be very costly in terms of resources. Second on the tables with frequents inserts notifications will be blinks.
In general, I understand that I am not convincing.
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
But the editing files is not a "chat" and not needed online here. _______________________________________________ Users mailing list Users@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/users