GNOME Bugzilla – Bug 314753
Changes of file read-only state ignored
Last modified: 2005-09-28 11:04:53 UTC
Please describe the problem: If you open read-only file in GEdit and then change the file to writeable (for example with chmod) there is no way to make GEdit note the change. This is especially annoying with some version control systems that implement their custom file system which manages write statuses of the files. Steps to reproduce: 1. Create file like /tmp/test.txt and make it read-only 2. Open the file in GEdit 3. Change file to writeable Actual results: GEdit doesn't note the change and there is no way (not event the "Revert" menu action) to make GEdit to recognize the situation. The only work-around is to close file and then reopen it. Expected results: The GEdit allows modifications to the file and saving as the file mode is changed. Does this happen every time? Yes Other information:
file monitoring it is something that has been discussed in various places... for now I'm marking this as dup of bug 114215, though I seem to recall that there is a t least another bug with a longer discussion and even a prototype patch. The summary is: active file monitoring sounds cool in theory, but brings a lot of headaches due to brocken support from the underlying system (gnome-vfs, FAM, gamin, inotify, dnotify etc) so at the moment is not a viable solution. In the mean time you can use File->Revert to make gedit notice that the file is not readonly anymore. *** This bug has been marked as a duplicate of 114215 ***