This is purely speculation, but I think I know the reason why this bug occurs.
I've been getting this problem constantly over the past few days. I'm using SSHFS to mount my remote web server, which has of late been a fairly high-latency connection.
I have a feeling that this has something to do with the way gedit handles modified stamps.
I think that the modified stamp on files aren't set until they are finished saving, and because it's a high-latency mount, saving takes a few moments. When I start trying to edit the file again, gedit checks to see if the file has been modified by checking stamps, but since I "saved" a few moments ago, and the modified stamp says that it happened once the file finished saving on the remote end, it thinks there was an edit.
The only way I could conceive of this being fixable is if gedit has a configuration option to disable checking the modified stamp, or ignores what it perceives to be recent "modifications."
This is purely speculation, but I think I know the reason why this bug occurs.
I've been getting this problem constantly over the past few days. I'm using SSHFS to mount my remote web server, which has of late been a fairly high-latency connection.
I have a feeling that this has something to do with the way gedit handles modified stamps.
I think that the modified stamp on files aren't set until they are finished saving, and because it's a high-latency mount, saving takes a few moments. When I start trying to edit the file again, gedit checks to see if the file has been modified by checking stamps, but since I "saved" a few moments ago, and the modified stamp says that it happened once the file finished saving on the remote end, it thinks there was an edit.
The only way I could conceive of this being fixable is if gedit has a configuration option to disable checking the modified stamp, or ignores what it perceives to be recent "modifications."