Community
Participate
Working Groups
a.modify an open file so that it is dirty and don’t save it b.select a tab different from the modified file c.close all editors d.You will be prompted to save the modified and over-written file, when you choose to save it, you will be told that the file has been modified on disk and asked if you want to over-write it, a user could say yes thinking that he already over-wrote the file but will lose the over-written changes, since the old modified file is saved. e.If the user chooses that he does not want to over-write the changes, the close all operation will have no effect on any open file. f.If the user chooses not to save the file, the over-written file will be the one on disk but the additional modifications that were made to the file will be lost and cannot be recovered from the local history. g.This happens because over-writing a file does not take effect immediately when its editor is dirty, when clicking on the file’s editors, a user will be prompted to re-load the file but this should happen automatically
Hanna, could you please compare against 2.1 to determine if this is a regression?
There is a missing step between 'b' and 'c': after 'b', you should drag and drop a file with the same name as the open file and confirm that you wish to overwrite it, then you close all editors. The same behavior exists in 2.1, as described.
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Remy is now responsible for watching the [EditorMgmt] component area.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
