Community
Participate
Working Groups
I have reproduced this bug on text editor and java editor. Scenario: - create a new file with 3 lines of text inside and save - Delete the 2 last lines - Save - Undo Typing (the 2 deleted lines come back and the file can be saved) - Delete the last line: here it is the bug => The file cannot be saved anymore !! For the scenario purpose, I start with a new file, but it works with an existing file. This bug has been also reproduced on Eclipse3.1RC4 on Linux Debian as OS.
Works for me using R3.1. Maybe I did some steps wrong, e.g. "Delete the last 2 lines" can be accomplished in many different ways ;-). Please provide more detailed steps if you see this using R3.1 or newer.
To delete a bunch of lines, I select them, and use the delete key. The 2 lines must be deleted at once. If I use the "delete line" key, I am not reproducing the bug (the 2 lines are deleted independantly). I produced also it on eclipse 3.1RC3 on windows XP (so, seems not to be linked to OS).
3.1RC3 is a release candidate and not R3.1. Did you see it on R3.1? Can you provide selection and caret for each step, e.g. do you have 111 222 333<caret><eof> or 111 222 333 <caret><eof>
I produced the bug on eclipse 3.1 (final release) on linux debian. I also produced the bug on eclipse 3.1RC3 on windows XP. It works with both your scenarii: This is the step I followed with the 1st scnenario 1) 111 222 333<caret><eof> => save 2) 111 <caret>222 333<eof> with <caret> to <eof> selected => hit the delete key and save 3) 111 <caret><eof> => undo typing 4) 111 <caret>222 333<eof> with <caret> to <eof> selected 5) 111 222 <caret>333<eof> with <caret> to <eof> selected => hit the "delete" key Bug: the file cannot be saved now Hope you have enough data :)
The editor thinks the file is not dirty (no * in the tab). Looks like a modification stamp bug.
Cannot reproduce with I20051222. I believe this could be bug 109104 which is in 3.1 has been fixed in 3.1.1 and 3.2 M2.
*** This bug has been marked as a duplicate of 109104 *** *** This bug has been marked as a duplicate of 109104 ***
Verified on 3.1.1
