Community
Participate
Working Groups
While editing an auto-generated *.java file and after starting to re-auto-generate so that the file is deleted, but not yet recreated... Touching the editor tab causes the 'do-you-want-to-save-contents' pop-up dialog. Yes => Save. No => Close. Reasonable. However since neither Yes nor No reverts, I choose to close the dialog. This does No, closing the editor, advancing to the consistent editor deleted state. However since I closed rather than Yes-ed/No-ed, surely it should take me back to the pre-dialog state. I should be able to view the (unsaved) text, possibly even copy it somewhere. The editor should not just close.
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. -- The automated Eclipse Genie.
Cannot be stale until some JDT committer triages it. I regularly find myself in the wanting to press the 'go-away-stupid-tool' button, so I hit close rather than the equally inappropriate Yes/No and lose work. Fortunatelty GIT staging or local history or Undo may come to the rescue. But unfortunately Undo is now intermittent if the debugger has done an incremental recompile.
Cannot be stale until some JDT committer triages it.
Changing to major since the current behavior leads to a loss of user work.
