GNOME Bugzilla – Bug 467306
Detect when a file is renamed
Last modified: 2020-11-24 09:57:09 UTC
The bug has been opened on https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/132788 "Binary package hint: gedit When you edit a file in gedit and the file is renamed, gedit doesn't notice that the file on disk has disappeared. Instead, when trying to save a file that has been renamed, a warning should appear, similar to the yellow warning bar that appears when a file content has been modified by another program. Steps to reproduce the problem: 1. Open a new file in gedit. Save it to ~/foobar 2. Rename the file ~/foobar to ~/foobar.new 3. Modify the file inside gedit (this step can be omitted) 4. Press the Save button A new file ~/foobar is silently written. No indication is given to the user that the file was not there when saving. Expected behavior: Show a warning that the file has been renamed, moved, or deleted. Ask the user whether she really wants to save the file under the old name (to the old location). Better yet, determine what exactly happened to the file (was it renamed, moved, or deleted). If the file has been moved or renamed, suggest to save the file in the new location or under the new name, respectively. ProblemType: Bug Architecture: i386 Date: Thu Aug 16 00:52:51 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/gedit Package: gedit 2.18.1-0ubuntu1 ..."
*** Bug 393034 has been marked as a duplicate of this bug. ***
Still in 3.2
Created attachment 287359 [details] [review] Allow user to save or don't save the file in case of file moved, renamed or deleted.
*** Bug 712606 has been marked as a duplicate of this bug. ***
*** Bug 746272 has been marked as a duplicate of this bug. ***
Mass-closing of all gedit bugzilla tickets. Special "code" to find again all those gedit bugzilla tickets that were open before the mass-closing: 2bfe1b0590a78457e1f1a6a90fb975f5878cb60064ccfe1d7db76ca0da52f0f3 By searching the above sha256sum in bugzilla, the gedit contributors can find again the tickets. We may be interested to do so when we work on a specific area of the code, to at least know the known problems and possible enhancements. We do this mass-closing because bugzilla.gnome.org is being replaced by gitlab.gnome.org.